Component properties are set according to the precedence of configuration path directories. For example, a configuration path might look like this:
<ATG9dir>/DAS/config/config.jar:<ATG9dir>/DAS/home/localconfig
Given this configuration path, properties that are set in localconfig always have precedence over those set in config. So, when Nucleus needs to configure the component /services/Sunny, it looks for Sunny.properties as follows:
<ATG9dir>/DAS/config/services/Sunny.properties<ATG9dir>/DAS/home/localconfig/services/Sunny.properties
If Nucleus fails to find Sunny.properties in the configuration path, it generates an error.
Configuration path versus CLASSPATH
An application’s configuration path and Java’s CLASSPATH behave differently as follows:
Configuration files found in the configuration path are merged, not replaced; and the last-found properties in configuration files have precedence over those found earlier.
.classfiles found earlier in CLASSPATH supersede files found later.
Note: Never place .class files in the configuration path directory path. Doing so can yield errors, as the .class files might interfere with Nucleus’ ability to resolve component names.
