To use cartridges, the Oracle Commerce Core Platform must create Nucleus components for the cartridge handler classes and any classes that the handlers depend on. The DAF.Endeca.Assembler
module includes Nucleus component configuration for Platform-level cartridge handlers in the /atg/endeca/assembler/cartridge/handler
and /atg/endeca/assembler/cartridge/handler/config
Nucleus paths. The Store.Endeca.Assembler
module includes component configuration for Commerce Reference Store-specific cartridges in those same Nucleus path locations.
In addition to the handler classes, cartridges rely on Experience Manager configuration and application rendering code. Because Experience Manager configuration and page rendering are both application-specific, the files that support all cartridges are included in the Commerce Reference Store modules.
The default folder that Nucleus will try to resolve cartridge handlers in is /atg/endeca/assembler/cartridge/handler
. The /config
subdirectory in that same location contains configuration components associated with the CartridgeHandler
components. Similarly, /atg/endeca/assembler/cartridge/handler/xmgr
and /atg/endeca/assembler/cartridge/handler/guidedsearch
folders contain cartridge handlers that are specific to Experience Manager and Guided Search, respectively, and they also have their own /config
sub-paths.
The components in the /atg/endeca/assembler/cartridge/manager
Nucleus folder provide additional cartridge support outside of what can be found in the cartridge handlers themselves. For example, the NavigationStateBuilder
and NavigationState
components build and represent the current navigation state, respectively; the DefaultFilterState
component represents the state of any filters; and the MdexRequestBuilder
component builds MDEX requests.
Note: Currently, the /atg/endeca/assembler/cartridge/handler/xmgr
and /atg/endeca/assembler/cartridge/handler/guidedsearch
folders are empty and function only as placeholders for future components.