Re: Preventing re-initialization or re-configuration

2007-03-21 Thread Dave Levitt
My gmail archive for this list doesn't go back too far. What is the time frame for that discussion? I assume searching for 'library configuration' should be a start. This may also be promoted to a FAQ or 'best practices' document [wiki page], so it becomes a resource to point to ["The consensus i

Re: Preventing re-initialization or re-configuration

2007-03-21 Thread Jacob Kjome
Ultimately, logging is the concern of the user, not the library creator. As such, the library creator should defer to the user to define the logging configuration (or not if the user doesn't want to). BTW, you'll find good list archives here http://marc.info/?l=log4j-user&r=1&w=2 Jake Quo

Re: Preventing re-initialization or re-configuration

2007-03-21 Thread James Stauffer
If you can pursuade the library author to make a change maybe you can persuade them to follow the best practices for libraries which strongly discourage explictit configuration. There is discussion about this in the archives. Setting up repository selectors might be helpful. On 3/21/07, Dave Le

Preventing re-initialization or re-configuration

2007-03-21 Thread Dave Levitt
I was trying to find out where my logging output was going in a J2EE application [WebSphere _and_ ATG Dynamo - things just don't get any uglier than that] When I enabled log4j.debug, I saw that the log4j system was being initialized twice, once by my log4j.xml and a second time from a log4j.prope