Commerce Reference Store stores the XML files that configure Experience Manager in the <ATG11dir>/CommerceReferenceStore/Store/Storefront/deploy/cartridge_templates directory. This directory contains sub-directories for the cartridges that are used in Commerce Reference Store. Each sub-directory contains:
A
template.xmlfile that configures the cartridge for use in Experience Manager. It defines the cartridge’s content type, as well as its properties and the editors for those properties. In order to support multiple languages in Experience Manager, these templates use resource bundle keys to refer to strings, instead of hard coding the strings directly in the templates.A 40 by 40-pixel thumbnail image for the icon that is displayed in the cartridge picker in Experience Manager.
A
/localesdirectory that holds resource files for strings used inside the template that require translation, for example, the template description. These resource files allow Experience Manager to display a localized version of each cartridge in a chosen language.
The JSP renderers for the cartridges that are used in Commerce Reference Store are located in the store.war/cartridges directory. The path to each JSP renderer follows this convention:
store.war/cartridges/cartridge-type/cartridge-type.jsp
For example, the path to the Breadcrumbs cartridge renderer is:
store.war/cartridges/Breadcrumbs/Breadcrumbs.jsp
Each renderer has its own directory, so that associated content (sub-pages, images, and so on) can be grouped together, making it possible for renderers to be packaged as stand-alone units. Providing a unique name for each renderer makes it easier to distinguish one file from another during various tasks such as editing.
Note: See Retrieving Renderers in the ATG-Endeca Integration Guide for details on how the correct renderer is retrieved for each cartridge.
