Henri, There are some bridges out there but none had a version number > 0.1. I found the simplest way was to configure JUL using a custom config file and then tell it to use my custom handler to forward all messages to log4j. There are obvious performance implications but it is doable and fairly simple since it didn't require any solr code changes.
- will -----Original Message----- From: Henrib [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 22, 2008 3:15 PM To: solr-user@lucene.apache.org Subject: logging through log4j Hi, I'm (still) seeking more advice on this deployment issue which is to use org.apache.log4j instead of java.util.logging. I'm not seeking re-starting any discussion on solr4j/commons/log4j/jul respective benefits; I'm seeking a way to bridge jul to log4j with the minimum specific per-container configuration or restriction. I've failed to find a way that would work for "all" servlet containers (Tomcat,WebSphere,Jetty) without disrupting SolrCode. My last current attempt that requires code modification is posted in last reply here http://www.nabble.com/logging-through-log4j-to13747253.html#a16825364. Comments/experience welcome. Thanks Henri -- View this message in context: http://www.nabble.com/logging-through-log4j-tp16825424p16825424.html Sent from the Solr - User mailing list archive at Nabble.com.
