If you put the properties files in your webapps classes dir, it will only apply to your webapp.
Try putting the properties files in your app servers classpath. With Tomcat you'd put them in tomcat/common/classes. -----Original Message----- From: Martin Monsorno [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 01, 2003 8:43 AM To: Niesen, Nathan Cc: 'Edgar Dollin'; 'Struts Users Mailing List' Subject: Re: how to switch of logging with log4j at initialization "Niesen, Nathan" <[EMAIL PROTECTED]> writes: > There is a bug in commons-logging 1.0.2+ that causes log4j to be used if > it's found in the classpath. Just remove the log4j jar from your webapps > lib dir. > > http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17561 > > There is also a bug in the commons-logging nightly build, which is what the > current Struts build uses, that causes the commons-logging.properties to be > ignored. > > http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17894 As I wrote as an answer to Edgar Dollin, my problem is not that log4j is used, but that my log4j configuration seems to be not the only one used, as I set the logging for "com.apache" to a file with ERROR level, but the output for (some of?) the commons-classes is logged anyway to stdout. -- Martin --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
