commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cost...@covalent.net
Subject Re: [discovery] Use of ClassLoader in ClassFinder
Date Wed, 26 Jun 2002 16:43:58 GMT
On Wed, 26 Jun 2002 rsitze@us.ibm.com wrote:

> One heads up...  The loader attempts to find a service using the context
> class loader, and failing that it tries the SPI Class's class loader.  This
> is NOT equivalent to Class.getName(), which would pick up the ClassFinder's
> class loader.
> 
> I believe this may be more appropriate.. but then again the SPI's Class
> Loader is more likely to be equivalent to the context class loader...
> thoughts?

What is SPI ? Sorry, too many acronyms.

It is likely that commons-discovery will be in the parent class loader,
while the discovered packages in child loaders. 

Probably the 'right' thing to do is also try the class loader of the 
caller ( it is possible to get access to the call stack - with some 
hacks - like we do in c-logging).

Costin



--
To unsubscribe, e-mail:   <mailto:commons-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:commons-dev-help@jakarta.apache.org>


Mime
View raw message