Configuring a BOD service module

Configuration files get loaded when their component is first called. The class loader automatically discovers the configuration directories, by following the naming conventions. When resolving configurations, custom configuration always takes precedence over the base configuration. At runtime, command developers can retrieve the configuration information by using the ComponentConfigurationRegistry Java class, which retrieves the class responsible for parsing and providing an interface to retrieve the information. There are two ways add configuration data to a service module. The first way is to extend the default HCL Commerce configuration XSD. This allows you to quickly add name-value pairs to the configuration data of an existing component. The second way is to define your own configuration file structure, and provide your own configuration file parser. This approach, while more complex, is quite flexible – everything from the structure of the configuration file itself to the implementation of the parser, can be changed.