> -----Original Message-----
> From: Peter Donald [mailto:[EMAIL PROTECTED]]
> Sent: den 22 november 2001 13:55
> To: Avalon Developers List
> Subject: Re: DefaultLogTargetFactoryManager
>
>
> On Thu, 22 Nov 2001 23:59, Leo Sutic wrote:
> > > -----Original Message-----
> > > From: Peter Donald [mailto:[EMAIL PROTECTED]]
> > > Sent: den 22 november 2001 13:37
> > > To: Avalon Developers List
> > > Subject: Re: DefaultLogTargetFactoryManager
> > >
> > >
> > > How about using the contextClassLoader first and then if that
> > > fails using the
> > > classes classloader ?
> >
> > I don't see in what situations that would help. All I see is a jumble of
> > class loaders. I think we should stick to the context class loader
> > throughout the code.
>
> And when the ContextClassLoader is not set ?
Java API for Thread.getContextClassLoader ():
"Returns the context ClassLoader for this Thread. The context ClassLoader is provided
by the creator of the thread for use by code running in this thread when loading
classes and resources.
If not set, the default is the ClassLoader context of the parent Thread.
The context ClassLoader of the primordial thread is typically set to the class loader
used to load the application."
So that should be "never", as I understand it. Do you have any examples when
getContextClassLoader () == null?
/LS
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
