Thanks iksrazal So you've reversed the problem by calling Init prior to initialising the correct configurator, thereby overwriting the xml-security configuration with your own. Is this right?
I still have my doubts about the xml-security library requiring its own log4j configuration. Can anyone confirm the requirement? 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/ >
