Re: Mulitiple virtual hosts and classloader strangeness

j.random.programmer wrote:
> To shed a little more light on my previous post,
> my class Foo is logging related and registers itself
> as a logger with the java.util.logging.LogManager
> class.
>
> One theory is that even though A.com and B.com have
> seperate class loaders, they still both share the
> same LogManager (part of the Java API).

This example illustrates why servlet-classloader-hack is not a good
idea. :-)

>
> If this explains the problem (does it?) then is there
> any known workaround for cases where classes (such
> as loggers) must be loaded seperately for different
> virtual hosts yet since the underlying registry
> is belongs to the system classloader (a JVM class
> like LogManager), we run into a problem.

It's possible, but it's something Resin probably needs to do, just like
JNDI, System.out, and System.getProperty.

-- Scott

>
> Best regards,
>
> --j
>
>
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Finance - Get real-time stock quotes
> http://finance.yahoo.com
Received on Mon 09 Sep 2002 08:33:47 -0700