commons-logging should be just as easy to use as log4j. I have used it in a standalone application with no problems, and it is nice that I can switch to a different logging implementation (i.e from log4j to JDK1.4 logging) without changing my code at all. The problem is using commons-logging in Tomcat.
Regards Jim. > -----Original Message----- > From: Peter Lin [mailto:[EMAIL PROTECTED]] > Sent: 19 February 2003 15:52 > To: Tomcat Users List > Subject: RE: Best Logging practices > > > > 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] > PLEASE READ: The information contained in this email is confidential and intended for the named recipient(s) only. If you are not an intended recipient of this email you must not copy, distribute or take any further action in reliance on it and you should delete it and notify the sender immediately. Email is not a secure method of communication and Nomura International plc cannot accept responsibility for the accuracy or completeness of this message or any attachment(s). Please examine this email for virus infection, for which Nomura International plc accepts no responsibility. If verification of this email is sought then please request a hard copy. Unless otherwise stated any views or opinions presented are solely those of the author and do not represent those of Nomura International plc. This email is intended for informational purposes only and is not a solicitation or offer to buy or sell securities or related financial instruments. Nomura International plc is regulated by the Financial Services Authority and is a member of the London Stock Exchange. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
