Component properties are set according to the precedence of configuration path directories. For example, a configuration path might look like this:

<ATG10dir>/DAS/config/config.jar:<ATG10dir>/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:

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:

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.


Copyright © 1997, 2012 Oracle and/or its affiliates. All rights reserved.

Legal Notices