MagnoliaConfigurationProperties instances provides access to system-wide configuration properties. They are
essentially a wrapper around all the
magnolia.properties files that are used in the system, as well as
properties configured in module descriptors, etc.
Implementations of this interface are responsible for locating relevant PropertySource, and provide them in a sensible order.
The following properties are required:
- magnolia.cache.startdir:
directory used for cached pages
- magnolia.upload.tmpdir:
tmp directory for uploaded files
- magnolia.exchange.history:
history directory used for activation
- magnolia.repositories.config:
repositories configuration
- log4j.config:
Name of a log4j config file. Can be a .properties or .xml file. The value can be:
- a full path
- a path relative to the webapp root
- a file name which will be loaded from the classpath
- magnolia.root.sysproperty:
Name of a system variable which will be set to the webapp root. You can use this property in log4j configuration
files to handle relative paths, such as ${magnolia.root}logs/magnolia-debug.log.
Important: if you drop multiple magnolia wars in a container which doesn't isolate system properties
(e.g. tomcat) you will need to change the name of the magnolia.root.sysproperty variable in web.xml and
in log4j configuration files.
- magnolia.bootstrap.dir:
Directory containing xml files for initialization of a blank magnolia instance. If no content is found in any of
the repository, they are initialized importing xml files found in this folder. If you don't want to let magnolia
automatically initialize repositories simply remove this parameter.