: > JULI can be configured per-webapp also by adding a logging.properties to the : > classpath (add it to WEB-INF/classes). So you can configure Handlers
: JULI is a Tomcat thing : (http://tomcat.apache.org/tomcat-6.0-doc/api/org/apache/juli/package-summary.html : ), right? In other words, it doesn't work w/ Jetty 6, as far as I can tell. Unless I'm missing something, org.apache.juli.* is a completley stand alone package providing a ClassLoaderLogManager that just about any java app using multiple classloaders could take advantage of. It could probably work with jetty just by registering it with the JVM as the LogManager class (using a system property) : I'd appreciate any insight on how to get Java Util Logging to play nice in : Jetty 6. Jetty6 shouldn't care about how you (or solr) use JUL at all ... a standard logging.properties (either globally or specified for the jetty instance using the appropriate system property) should work fine. that won't give you any fancy per webapp configuration -- but that's what you get for free if you use Jetty. If you use Tomcat (or especially Resin) you get a lot more bells and whistles for the JUL configuration. -Hoss
