> > I can't move log4j.jar to the system classpath, because then it > > will be visible to all webapps
> It was already visible to all webapps when the jar was in Tomcat's lib > directory, so moving it > should not matter. The local copies in WEB-INF/lib *should* be found > before the system > classloader is requested. Note that in order to get individual use of > log4j by a webapp, > each must have its own log4j.jar and log4j.properties. According to the http://tomcat.apache.org/tomcat-6.0-doc/class-loader-howto.html classloader howto , the order is: system classloader, webapp classloader, common classloader. So I'll get a global RepositorySelector if I move log4j.jar to the startup classpath. -- View this message in context: http://www.nabble.com/Seeking-authoritative-answer-re-using-Log4J-with-v6-tp24225048p24225392.html Sent from the Tomcat - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
