tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bob Jamison <rjami...@lincom-asg.com>
Subject TC4's classloader choking on xerces.jar (maybe)
Date Tue, 21 Nov 2000 18:51:59 GMT
After I posted the msg the other day about my problem, I have
heard from two others who are having the same thing happen.

This happens when you have a web-app that uses xerces.jar
in its WEB-INF/lib directory.  Jasper's classloader, apparently
while loading dependent classes referenced from within Xerces,
gets the notion that your app is attempting to load classes from
outside the classloader's bounds, which creates a 'sealing error.'

(Either that,  or the other way around: dependencies have
confused Tomcat into attempting to load its own classes
from xerces.jar)

I have tried renaming the jar file, and also unpacking it into
WEB-INF/classes, to no avail.   I cannot pull the files similar
to Crimson's out,  as our package then will not function outside of
Tomcat.

Of course, Tomcat could be hacked to accomodate Xerces,
but that would destroy the idea of  having "drop-in" apps
in the app server.


Any ideas?  I have been looking at URLClassLoader's code,
to see if a quick-and-easy extension can cure this problem.



Bob Jamison
LinCom Corp


Mime
View raw message