Hi --<br><br>An existing project of mine uses log4j. This project<br>also embeds a Jetty server. In trying to upgrade<br>from Jetty 5 to Jetty 6 all of the Jetty logging<br>started going to stdout and Jetty says it will do
<br>something different if it finds an slf4j.Logger on<br>the classpath.<br><br>Ok, so I found slf4j-api-1.1.0-RC1.jar and<br>log4j-over-slf4j-1.1.0-RC1.jar, and put them on<br>my classpath, removing the former log4j-1.2.14.jar
.<br>Looks like a great idea.<br><br>I haven't gotten as far as figuring out whether<br>Jetty understands this as some things that<br>I was using in log4j do not seem implemented<br>in the log4j-over-slf4j classes.<br><br>
Namely --<br><br>org.apache.log4j.Logger<div id="mb_0"> .setLevel(Level)<br> .getLevel(Level)<br> .isEnabledFor(Level)<br>
.log(Level,Object)<br> .log(Level,Object,Throwable)
<br><br>Other things I need are missing, like org.apache.log4j.Level<br>but by putting the old log4j log file on the classpath after<br>the slf4j I get past that but not<br>the missing methods on Logger. Is using the log4j.jar
file<br>in addition to the two slf4j jar files the way to go about this?<br><br>Reading the list archive, I sense some of this may be <br>by design, but I'm not sure. Can someone clarify
<br>if I am doing this right?<br><br>How would you integrate Jetty 6 and it's new slf4j<br>requirement into an existing log4j enabled project<br>using slf4j?<br><br>Thanks,<br>Mike<br></div>