Yoav Shapira wrote:
Hola,
> Mmm, I'd hate having endorsed classes depend on commons-logging ;(
Could you expand this thought?
It's a simple thought, like I said, shooting from the hip.
Commons-Logging has an unfortunate history
(http://www.qos.ch/logging/thinkAgain.jsp), and the deeper / higher it
is on the classpath, the worse the potential. It doesn't get much
deeper on the classpath than the endorsed repository, so putting
commons-logging there made me instinctively cringe a bit.
This article is total FUD, this should be obvious. Actually, log4j is
one of the libraries which has been causing the most problems in Tomcat
(the most being held by Xerces, which thankfully is now solved).
If you want to say bye bye to logging problem, it's easy: we need to
switch Tomcat to java.util.logging (with an appropriate LogManager and
Handlers, of course).
Rémy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
