Logging configurator

Description

LoggingConfigurator resposibility is setting up the Log4j. It was introduced so that log system configufration were preformed in a way uniform with oterh parts of the system.

At this point the configurator retrievs a configuration InputSource from the configuration factory (it will get validated agains apropriate schema), parses it and passes on to Log4j DomConfigurator. In the future we may want to iterate over the configuration ourselves and instantiate the needed objects (appenders etc. The Pico Way). This will allow a number of neat things, including Appenders wrinting to Ledge FileSystem. Until then paths in the conifguration files need to be either absolute in the machine's FS, or relative to the container's working directory.

Functionality anticipated in the future

  • runtime modification of logging configuration, most notably logger verbosities
  • management of loggers through textual interaction, and possibly JMX
  • customized log4j file appenders working over Ledge FileSystem

Browse

  • LoggingConfiguator JavaDoc
  • LoggingConfiguator XRef
  • LoggingConfiguator CVS log
  • Log4j documentation
  • LoggingConfiguator configuration file schema generated from DTD provided with Log4j
  • LoggingConfiguator configuration file example

Dependencies

required components ConfigurationFactory
required libraries Log4j (log4j)

Constructor parameters

position type descritpion
1 org.objectledge.configuration.ConfigurationFactory The configuration factory to load configuration from.