I just noticed the typos in my post. what I meant to say is, use log4j since commons-logging uses it.
using commons-logging will require more work than using log4j directly. there are numerous examples distributed with log4j, including how to extend it with custom logging categories. sorry for any un-intentional confusion :) peter --- "Collins, Jim" <[EMAIL PROTECTED]> wrote: > I would not recommend using commons-logging in a > web-app. If you want to > separately configure the logging requirements of an > application you have to > deploy it with its own logging properties file > (log4j.properties for log4j). > For commons-logging to pick up your apps logging > properties file you need to > deploy commons-logging.jar in yourapp/WEB-INF/lib. > This should not be a > problem however having commons-logging.jar in > yourapp/WEB-INF/lib and > common/lib causes Tomcat to crash. I have had this > problem and so have a > number of other people. So avoid the heartache of > this and log directly to > log4j or the JDK1.4 logger. > > Regards > > Jim. > > __________________________________________________ Do you Yahoo!? Yahoo! Shopping - Send Flowers for Valentine's Day http://shopping.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
