You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by bu...@apache.org on 2004/03/06 22:55:55 UTC
DO NOT REPLY [Bug 25156] -
[logging] Enhance error message for " org.apache.commons.logging.impl.Log4JLogger does not implement Log"
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25156>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25156
[logging] Enhance error message for " org.apache.commons.logging.impl.Log4JLogger does not implement Log"
craig.mcclanahan@sun.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
------- Additional Comments From craig.mcclanahan@sun.com 2004-03-06 21:55 -------
I've improved the error message in the (fairly common) case where the user has
org.apache.commons.logging.Log available more than once in the class loading
hierarchy.
For the expected configuration when using commons logging inside Tomcat, you
should consult the Tomcat documentation, but I've had no problems with the
standard way that Tomcat packages things (commons-logging-api.jar in common/lib,
no logging libraries in my webapp, put log4j.jar in commons/lib if I want to use
it).
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org