Hello Peter! Reacting to your request support for supplying Log4J configuration via FortressConfig.setLoggerManagerConfiguration() has been added. It was me who submitted the patch, but unfortunantly I've got no experience with Log4J.
Can somebody with Log4J experience and interest in Fortress please test the latest version available in the CVS? Peter Severin, I hoped, you would participate ! ;-) The feature is implemented in the following way: ContextManager.java in the initializeLoggerManager tests if a) there is a version="log4j" attribute on the root node of the supplied configuration file b) the name of the root node is log4j:configuration if any of this is true then an attempt is made to create Log4JConfLoggerManager, feeding the configuration to it. The code has not been run a single time, so testing badly needed. It is also utimately necessary to proofread and improve the section of ContextManager.java that does this. WBR, Anton Tagunov PS> I am participating in developing a new project and I am intrested to use PS> avalon/fortress in a servlet container environment. PS> On tomcat startup log4j complaints... PS> Doing only setLoggerManagerConfiguration() doesn't do the trick. PS> Fortress continues to use logkit --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
