Cascading Configuration Files

Starting with Wrapper version 3.0.0, it is possible to specify "include files" within a configuration file like cascading style. This is useful where there is a need to override default values without modifying the main default configuration file "wrapper.conf".

Syntax:

Include files are specified by placing a line in the configuration file with the following syntax:

#include ../conf/wrapper2.conf

Layer Depth:

Include files can be nested up to 10 levels deep with cascading style.

Property Priority:

The order of where within a file you should put the definition of the include file is important. If there are the same name of properties in the configuration files, you should pay attention to the order.

The definition of "#include" line should be placed at the very bottom of the configuration file. For example, the "wrapper.conf" file includes "File2.conf" and the "File2.conf" file includes "File3.conf". In addition, the property "PropertyX=valueX" is defined in EACH of the three files. In this case, the property value "PropertyX=value3" of "File3.conf" will be set after processing all files.

On the other example, properties set after the included file will override properties settings within the included files.

This rule applies to the all contents of include files as well.

Path:

If relative paths to the include files are specified, be aware that all paths must be relative to the location of the Wrapper working directory. By default, the working directory is the location of the wrapper.exe file on Windows, or of the script used to launch the Wrapper on UNIX. The working directory can be changed using the wrapper.working.dir property, but this does not take effect until after the full configuration file has been loaded. This means that relative include file references will always be relative to the original working directory of the Wrapper.

#include.required ../conf/wrapper-settings.conf

#include.debug