See my other message for the reasoning. I would recommend not to use commons-logging in your code. It does nothing for you and can only cause problems. Just use Log4j directly. If other apps use commons-logging such as Struts, you'll obviously have to include commons-logging, but don't let it influence you to use it directly. Seriously, I've never seen it do any good and only bad. Check out...
http://marc.theaimsgroup.com/?l=log4j-user&m=102640868804904 http://qos.ch/logging/thinkAgain.html Commons Logging was my fault http://radio.weblogs.com/0122027/2003/08/15.html Jake Quoting Jerald Powel <[EMAIL PROTECTED]>: > > I have put down to the method not found thing to I my importing > java.util.logging.LogManager! I have since acquired the JAR from Apache.org, > implemented: > > public void contextDestroyed(ServletContextEvent event) { > org.apache.log4j.LogManager.shutdown(); > } > > in a servlet implementing ServletContextListener. So fingers crossed. I still > dont know why this error might be thrown, and resolved by this, when I am not > using log4j! (I am using incidentally using the org.apache.commons.logging > stuff) > > many thanks > > G. > > > --------------------------------- > Yahoo! Messenger - Communicate instantly..."Ping" your friends today! > Download Messenger Now --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
