http://bugzilla.slf4j.org/show_bug.cgi?id=190 Olivier Lamy <olamy@apache.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |olamy@apache.org -- Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

http://bugzilla.slf4j.org/show_bug.cgi?id=190 Hugues Malphettes <hmalphettes@intalio.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hmalphettes@intalio.com --- Comment #2 from Hugues Malphettes <hmalphettes@intalio.com> 2011-01-28 07:33:45 CET --- Hi Ceki and Olivier. Tomcat uses its own facxade for the logging framework. They have a simple Log interface with what one would expect out of those things and a hardcoded implementation for it: In org.apache.juli.logging.LogFactory public Log getInstance(String name) throws LogConfigurationException { return DirectJDKLog.getInstance(name); } The javadoc says: There is no discovery mechanism at all. Please use a different jar with a different source to return a different Log implementation. So Olivier's version of the juli's LogFactory must look like this: return SLF4JLog.getInstance(name) I am looking into eventually adopting the tomcat versions of jasper for the upcoming jetty-8 with servlet-3.0 and jsp-2.2 support. Tomcat jasper uses this logging faxcade and in that context we would be interested into an implementation of juli-over-slf4j. -- Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.