Chris,
My view on the question is as follows: Log4j configuration is the responsibility of the end-user or generally the application deployer. Whenever possible, a library should not try to configure logging but leave it to the deployer. After all, logging output is useful only if someone will take the time to look at it. If the end-user wishes to log then she should control the logging configuration. Nevertheless, it is very helpful if the library developer provides documentation on logging preferably with working examples. Is this in any way convincing? Regards, Ceki At 18:38 26.11.2001 -0500, you wrote: >Greetings, > >I'm wondering what strategy people are using to blend log4j.properties files between >different applications. Internally, we are handling this using Ant -- concatenating >all of the disparate log4j.properties files into a single file during the build >process. This works fine because we only allow one Root Category. > >But what about when one brings in another application (i.e JAR file) which also uses >log4j?? In this case, there is a sort of race condition. Both apps are trying to >define a Root Category, and only one is allowed. Any ideas?? > >Thanks, >-- Chris > >Chris Berry --- [EMAIL PROTECTED] -- 512-323-9479 > >-- >To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> >For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
