From another user's e-mail, there is a thread talking about detecting if log4j is configured - is that advisable for a library?
Like I said previously, logging is not your concern, but your user's concern. I see little reason for needing to detect whether it is configured or not. As a user, even if it is configured once, you would want your own to take precedence. So who cares if it has been configured previously. However, if you insist on wanting to do this, the wiki has a way to detect if logging is configured (I see you found it in your second email). Log4j-1.3, I believe, has a more robust mechanism to detect this. You might want to try it.
But from your mail - I am now sure of one thing. If by mistake, log4j is configured a second time inside the library, the user's root logger and other loggers would lose the settings from configuring the first time.
Is this a correct conclusion?
Yep, but only within the current logger repository. If you haven't defined a repository selector, the only logger repository available will be the default one. If you use a separate logger repository to do configuration, then you won't stomp on anyone else's configuration.
Jake
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
