Guidelines for JSP extensibility
This topic provides general guidelines for JSP extensibility. However, it is not
applicable to the login and logout
store-container.jspis the main JSP for the entire AngularJS Sterling Store Engagement application. It loads all the required
CSSfiles and calls all the required mashups and populates the output in the appropriate providers. It includes different
JSPsthat take over these individual tasks. This JSP also contains the main layout of the HTML content rendered on the page as header, main content and footer. The
store-container.jspfile also includes
store-extn-include.jsp, which is meant to add custom extensions and thus does not contain any content by default.
store-container.jspis not recommended and it should not contain any custom code.
- Since the
store-extn-include.jspfile is imported last in the
store-container.jspfile, you can use it in the following manner:
- Add new mashup calls, validations, rules and populate your own custom providers with the new data.
- Change or override the default values for providers.
store-extn-include.jspshould be placed in the
- If you are using third-party libraries, then you must add them in
store-extn-include.jspto ensure ease of upgrade.