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 Levitt <[EMAIL PROTECTED]> wrote:
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.properties file inside a library. The library is explicitly calling BasicConfigurator.resetConfiguration() ; And then reconfiguring from its own internal copy of log4j.properties, which does nothing useful for my debugging. So, I'm now looking for one of two things, either: A way to initialize the log4j system that can block later attempts to reconfigure it or A simple test that I can persuade the library author to implement that will say 'its already configured - don't do anything'. Like performing a LogManager.getCurrentLoggers() and seeing if it contains anything. [its a political impossibility for me to alter the library source code]. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- James Stauffer http://www.geocities.com/stauffer_james/ Are you good? Take the test at http://www.livingwaters.com/good/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
