xml-xalan-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 4574] - javax.xml.transformer.FactoryFinder#newInstance fails when called from servlets
Date Sat, 03 Nov 2001 03:02:29 GMT
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=4574>.
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=4574

javax.xml.transformer.FactoryFinder#newInstance fails when called from servlets





------- Additional Comments From ueno@unixuser.org  2001-11-02 19:02 -------
Sorry, I had missed reading the comment at the beginning of build.xml,
although I'm using Xalan 2.2D12 checked out from CVS.  Some time ago I
checked out xml-commons together with xml-xalan, and rebuilt it from
scratch.  The situation however, didn't change unfortunately.

It seems that Tomcat 3.2.3 coordinates the context ClassLoader
regarding WEB-INF/classes, lib for each servlet, but doesn't relate it
with the current thread, thus Thread#getContextClassLoader() returns the
parent ClassLoader.

What I would like to know is, why not go on using the current
ClassLoader simply or otherwise respect the current ClassLoader when
the context ClassLoader fails to load the provider class?

Regards,

Mime
View raw message