--- Jem Mawson <[EMAIL PROTECTED]> wrote: > Hello > > I note that the Init class performs Log4j > configuration using the > config.xml from within the xml-security.jar. This > has the unfortunate > side-effect of removing any Log4j configuration that > may have been set > from the application context. > > Is it possible to avoid using the configurator if > the rootlogger is > already configured with appenders? Or should the > Log4j configuration only > occur in the test classes and be omitted from the > xml-security library > proper? > > Cheers > Jem >
My solution - which incidently increased the performance dramatically - was to change the default level to warn and intialize log4j via PropertyConfigurator and a servlet on startup. The config file is read via getResourceAsStream out of WEB-INF/somedir . That allowed a custom config - catches all the axis stuff etc as well. The classloader sequence should load jars first, then allowing an overwrite by a servlet on via load on startup. As an aside, I use logging from http://protomatter.sourceforge.net/ for my app logging to avoid problems like these. HTH, iksrazal __________________________________ Do you Yahoo!? Yahoo! Small Business $15K Web Design Giveaway http://promotions.yahoo.com/design_giveaway/
