You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by bu...@apache.org on 2003/02/22 01:03:38 UTC
DO NOT REPLY [Bug 17279] -
Axis does not work when installed in WEB-INF/lib
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17279>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17279
Axis does not work when installed in WEB-INF/lib
------- Additional Comments From stevel@apache.org 2003-02-22 00:03 -------
Classloader trouble. hmmm. I would be tempted to file this with Sun as a defect.
Actually I'd be temped to file the entire current design and implementation
classloaders as a defect but that's a side issue.
The problem is, as if you look at the man page for Thread.getContextClassLoader,
it says "The context ClassLoader is provided by the creator of the thread for
use by code running in this thread when loading classes and resources."
So our code is meant to use the context classloader, as it is the one provided.
If we start using the class-specific classloader you have fun in those
situations where java.* classes are installed in an endorsed directory (as
java1.4 often requires), we end up in the situation where things like the
FactoryFinder cant find stuff as they were loaded in the wrong classloader.
Maybe we should factor out something that tries first against the thread
classloader and secondly against the class classloader to load a class, and use
it in this instance.