Ledge Container
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.
Functionality anticipated in the future:
Logger factory plugs into the container using
component customization mechanism,
and provides components that declare a dependency on a DNA Logger (using a
org.jcontainer.dna.Logger component parameter) with an initialized and ready to
go logger instance.
Configuration factory plugs into the container using
component customization mechanism,
and provides components that declare a dependency on a DNA Configuration (using a
org.jcontainer.dna.Configuration component parameter) with an initialized
configuration object.
The contents of the configuration object are read from an XML file, and verified against a RelaxNG schema.
Functionality anticipated in the future
org.jcontainer.dna.Configurableinterface.LedgeContainer is a NanoContainer flawor, that uses the
FileSystem component for
loading the composition file, and parses it using
Ledge XMLFrontEnd. It also pre-feeds
the internal PicoContainer with objects required by various container subsystems, including
a FileSystem, ClassLoader and confiuration directory path.
Allows running Ledge applications from the command line. After the continer is started
and components are composed and configured, a designated component is looked up and method
void main(String[]) is invoked on it. Note that it this mehtod should be
non-static so it may take advantage of the actual component instance composed by the container.