tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Remy Maucherat <>
Subject Re: Why commons-logging-api.jar?
Date Thu, 24 Apr 2003 19:58:18 GMT
Ceki Gülcü wrote:
> At 08:29 PM 4/24/2003 +0200, Remy Maucherat wrote:
>> The non delegating CL in Tomcat 4 is nothing but a source of problems, 
>> which cannot be implemented to actually work. You need to have an 
>> endless supply of particular workarounds for various libraries to 
>> avoid class conflicts.
>> I think in the case of log4j + c-l, there are issues if you attempt to 
>> override. Personally, I like JDK 1.4 logger better, because it's 
>> hassle free, and I have yet to see it cause applications to fail. I 
>> still have a really annoying bug report open, which seems to be caused 
>> by log4j, and which would also indicate that log4j creates CL 
>> problems: bug 3888. You seem to insist that it's Tomcat's fault, though.
> The bug report is available here:
> As you can see and read, all I have done is correct the log4j bug 
> reported by
> Jacob Kjome possibly related to 3888. As far as I can tell, that log4j
> bug as reported by Jacob has been solved in log4j 1.2.8.
> Jacob Kjome has gone to great lengths to make the bug reproducible. He
> also stated on 2002-11-01 01:53 that bug #3888 was not caused by log4j.

I should have logged a full trace for that error. That would have helped 
fix and debug issues.

I'm open to experiment with log4j in 5.x (since we have time to back out 
if there are issue).


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message