--- Jem Mawson <[EMAIL PROTECTED]> wrote: > 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?
More or less. I prefer to do the xml-security Init via servlets on startup also, so its guaranteed to happen and its only done once. So far its worked well. But again, from my understanding this works cuz the jars are loaded first, Init hasn't been called yet, my init servlet loads the log config and then finally calls xmlsec Init. This works for tomcat - whose classloader works that way - but you may have to be careful for something like Websphere whose classloader sequence is configuarable. In the end Log4j is a singleton and therefore only unique per jvm. > > I still have my doubts about the xml-security > library requiring its own > log4j configuration. Can anyone confirm the > requirement? > I can guess and say that the xml-security project has their own unit testing that needs logging, the scope is really independant of things like axis and servlet containers, and just about every apache project that produces jars also has log4j config files. So its up to you to use your own config. IMHO. HTH, iksrazal __________________________________ Do you Yahoo!? Yahoo! Small Business $15K Web Design Giveaway http://promotions.yahoo.com/design_giveaway/
