if you want to change the logging implementation then the stuff with the context classloader should mean that each web application should get it's own instance of the factory and each factory should use the classloader to load the commons-logging.properties file which defines it's behaviour.
if you mean the properties of the underlying logging system then that's a matter for the underlying logging system (rather than commons-logging).
- robert
On Monday, October 13, 2003, at 08:22 PM, Will Jaynes wrote:
Todd,
With the jars configured as you describe, how do you configure different logging properties for each web app?
Todd Jonker wrote:Will, what I suggest is placing c-l.jar in your server-level classpath, or in the JVM classpath... and **nowhere else**. If you have any custom Logs or LogFactory or anything put that in the same place. Then you can be sure that each web-app will use the same classes. This is what I am currently doing. I have code USING c-l at both the server level and at the app level, and it all works fine. Putting the same jar at the server level *and* at the web-app level seems to be asking for trouble. .T.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
