Reading thru the Log4J docs it seems that the recommended method for activating loggers is to have a static class member hold a logger instance at the class level.
With this approach the loggers are only added to the named hierarchy when the class is loaded. I was wondering if anybody had given any thought to the idea of pre-defining logger hierarchy names in advance of the related class being loaded (a sort of named hierarchy metadata). This would allow a GUI process to discover the available hierarchy names and define a configuration file that could be used irrespective of whether the class has loaded or not. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
