I have hit the same situation with software that requires use of Apahce commons logging, I use slf4j (and have it feed log4j); it has adapters to let you log from j.u.l and commons logging. I don't know if it's best practice, but it certainly works. ■ DOUGLAS E. WEGSCHEID // LEAD ENGINEER (269) 923-5278 // douglas_e_wegsch...@whirlpool.com "A wrong note played hesitatingly is a wrong note. A wrong note played with conviction is interpretation."
BRUNO MELLONI <bruno.mell...@chickasaw.net> 01/11/2012 05:56 PM Please respond to "Log4J Users List" <log4j-user@logging.apache.org> To "log4j-user@logging.apache.org" <log4j-user@logging.apache.org> cc Subject Log4j and Java7/JDBC4.1's CommonDataSource.getParentLogger() Just upgraded from Java 6 to Java 7 and got a nasty surprise. I have a class that extends from JDBC's AbstractDataSource. Java 7/JDBC4.1 requires implementing the abstract method getParentLogger() from CommonDataSource. The method returns a java.util.logging.Logger, but I use log4j. I imagine that this problem has been encountered before and solved. What is the best practice solution?
