Yoav, Given the severity of the logging problems I had with my Tomcat-based web-site yesterday, I am still under shock. (Yoav, many thanks for your help by the way.) It will take me a few days to recover and think of a solution with a cool head. Thus, I won't further comment on the matter although I obviously share your concerns.
At 09:40 20.02.2003 -0500, Shapira, Yoav wrote:
--Hi, I guess the subject pretty much says it all. I've been seeing a ton of issues people have when trying to use commons-logging. Some have to do with tomcat and complicated classloader issues, some have to do with apps that just use commons-logging (e.g. struts) and so users don't have the option to NOT use commons-logging. My question is, can we, should we, do anything to make log4j and commons-logging play better with each other? Or it is not log4j's job? Or is there nothing log4j can do about it? Personally, having used log4j for a long time and loving it, and having tried commons-logging a couple of times, I like using log4j by itself. I don't think the added complexity (configuration, deployment) of commons-logging is worth the effort at all. What do people think? Yoav Shapira Millennium ChemInformatics
Ceki
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
