Application container

store-container.jsp is the main container JSP file that contains the logic to load the resources required by the application. The JSP partials that are included in the main container JSP file are mentioned in the following table:

Table 1. JSP partials in main JSP file

File	Description
store-container-css-inlcude.jsp	Loads the CSS files required by the application.
store-container-vendorscripts-include.jsp	Loads the vendor JS files.
store-container-peretzscritps-inlcude.jsp	Loads the peretz JS files.
store-resource-include.jsp	Loads the application JS files.
store-data-inlcude.jsp	Loads the application data required as configuration.
store-datatype-include.jsp	Loads the datatype configuration required for the application.

The third-party libraries used in the application are as follows:

• CSS - Peretz CSS (IBM commerce theme of Bootstrap CSS)
• JavaScript
  • "angular": "1.4.7"
  • "angular-animate": "1.4.7"
  • "angular-aria": "1.4.7"
  • "angular-touch": "1.4.7"
  • "angular-i18n":"1.4.7"
  • "angular-messages":"1.4.7"
  • "angular-sanitize": "1.4.7"
  • "angular-bootstrap": "0.14.3"
  • "angular-ui-select":"0.13.2"
  • "i18next": "1.10.3"

The container invokes configuration related mashups and makes the retrieved information available in a JavaScript environment. The container supports the application in production and development mode. In the production mode, the minified files are loaded whereas in the development mode, the individual files are loaded.

• If the application is built and deployed as wscdev.war, then by default, the application runs in development mode.
• If the application is running in production mode, then to test the application in development mode, append appMode=dev in the URL parameters and reload.
• If the application is running in development mode, then to test the application in production mode, append appMode=prod in the URL parameters and reload.