ws-mirae-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aishwarya R" <>
Subject Log4j problems in Tomcat 5.x
Date Tue, 21 Nov 2006 20:09:55 GMT
I switched from Tomcat 4 to 5, and ever since have had unsolvable
problems with logging. In short, the commons logger refuses to use
Log4j. This would be fine for Tomcat itself, but all of my classes that
use commons-logging get taken over in this way. i have moved my own
code to use Log4j directly (so I know it works, and is configured
correctly, and is in the classpath of the context), but all of my jars
that use commons are out of my control.
If I try and force commons to use log4j, ( with
er in a file in /WEB-INF/classes), it gives
me a ClassNotFound exception, no matter where I place the log4j jar.
I have seen many messages on this list related to this issue, but no
solutions. Has anyone come up with anything? Aishwarya <>

View raw message