Chris,
I think you are absolutely right, if JULI's LogManager was registered.
In that case LogManager.reset() will go to ClassLoaderLogManager which
will only work on loggers that were associated with the thread's context
class loader before. The JDK implementation of the LogManager will
however
This is a problem that appears when embedding Tomcat into another
application. I observed it using Tomcat 6.0.24.
I am using JDK logging and I would like to make sure that Tomcat JULI
does not modify logging runtime configuration that is not owned by
tomcat or web apps running on tomcat.
Here is
ok, done.
Thanks,
henning
Am Mittwoch, den 03.02.2010, 13:08 +0300 schrieb Konstantin Kolinko:
> public class MyCatalina extends Catalina {
> >public Server getServer() {
> >return this.server;
> >}
> > }
> >
---
Hi,
this is a question about embedding Tomcat into an application so that
it can still be configured using server.xml and web applications can be
added or removed programmatically.
I am using Tomcat 6.0.24.
The way I tried to make it work is by instantiating an instance of
Catalina, feedi
