On Fri, Jun 19, 2009 at 6:50 PM, Emmanuel Bourg<ebo...@apache.org> wrote: > Don Brown a écrit : >> >> Sure, but that's kinda my point - many webapps, ours (Atlassian) in >> particular, cannot assume a specific application server. Our apps >> must be able to be dropped into any app server, with any other >> webapps, and still be expected to play nicely. Even inserting a root >> logger that filters for packages don't help, as another app could be >> using the same library. Again, all other serious logging libraries >> support this, what I would label, basic feature. Even commons >> logging, with all its flaws, allows us to reimplement their API's (in >> an OSGi environment) to handle the logging, but since JUL is a java.* >> package, we're stuck. > > I wouldn't be surprised if all other application server had the same > mechanism implemented by Tomcat. Ensuring webapps isolation is a basic > feature for the servers. That's definitely worth checking though.
They don't, AFAICT. Even if they did, it doesn't really help for us using OSGi. With Log4j, we control the instances of the Log4j classes, and therefore, are able to properly configure logging across multiple classloaders (bundles) that don't inherit from the web app classloader. Since JUL is in java.*, we have no way to cleanly (or any other way) configure logging for one webapp and its classloaders (via an embedded OSGi container, in our case). Don > > Emmanuel Bourg > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
