commons-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andreas Schildbach <>
Subject [commons-logging] Initialization of JDK1.4-Logger
Date Thu, 05 Aug 2004 15:31:19 GMT
I'm current developing an application that directly uses the JDK1.4 
java.util.logging-Framework. However, it also utilizes a framework 
(Spring) that uses commons-logging for logging.

Ideally, I'd like to set log levels at one central place. For my 
application, the choice is easy: I'm using one and 
append -Djava.util.logging.config.file to the JVM options.

Unfortunately, commons-logging seems to do its own programmatic 
initialization of the JDK logging component: my configuration file is 
ignored for all output of the Spring framework. One of the authors of 
Spring claims that Spring is not doing any special. I also found no 
mention of this issue in the docs/faq.

My question: How can I make commons-logging to _not_ initialize the 
underlying logging component and use the default configuration mechanism 
of the component instead?

The issue in Spring JIRA:



To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message