You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@xalan.apache.org by bu...@apache.org on 2001/10/04 15:26:47 UTC

DO NOT REPLY [Bug 2399] - ClassLoaders for WAS Often Fail on compiled classes.

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=2399>.
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=2399

ClassLoaders for WAS Often Fail on compiled classes.





------- Additional Comments From tom.amiro@sun.com  2001-10-04 06:26 -------
>From Seth Ford
--------------
The problem happens when the default classloader is not being used. So in a
case where you would use a XSLTC as part of a web application. i.e. packaged
as a WAR (Web ARchive). The container uses it's own classloader to resolve
dependencies and fails with a an "invalid method name". This only occurs
when using "-" or leaving an empty value for a variable.  If you have all of
the jars in your classpath this error will not occur because the Servlet
engine will resolve classes from the default classloader. I believe that
this is a J2EE spec, so I assume that it is occurring in all Servlet
Engines.