It sounds like this is more of a log4j configuration question then a commons logging question.
The answer is probably going to depend on the application server you're using. According to the Java Servlet 2.3 (and 2.4) specification, "The web application classloader must load classes from the WEB-INF/classes directory first, and then from library JARs in the WEB-INF/lib directory," so it appears you application server is off-spec, at least based on your description. But before getting into that, I'd ask why you need xDoclet.jar in a web application classpath? I'm not a big xDoclet user, but this seems odd to me. Justin -----Original Message----- From: Shishir K. Singh [mailto:[EMAIL PROTECTED] Sent: Sunday, March 28, 2004 3:08 AM To: Jakarta Commons Users List Subject: commons logging issue Hi, I am using the commons log for debugging in my web application. I have defined org.apache.commons.logging.Log=org.apache.commons.logging.impl.Log4JLogg er in the commons-logging.properties file. I also have the customized log4j.properties file in my WEB-INF/classes directory. However the Classloader for log4j when looking for the log4j.properties loads it from xDdoclet.jar that is present in my lib directory instead of loading it from the classes directory. How can I get around this behavior without specifying -D option on java. Thanks Shishir --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
