Are you using a geronimo plan with
<context-priority-classloader>true</context-priority-classloader>
for your web app?
I think it's likely that we added axis to geronimo between early jan and now.
If this doesn't work (I think there is a reasonable chance it will cause other problems) you might need to assemble geronimo using the versions of axis and xerces you need.
What happens if you use the versions of axis and xerces that geronimo uses? Are our versions out of date? If we actually implemented j2ee web services would that also solve the problem :-)?
thanks david jencks
On Jan 27, 2005, at 7:51 AM, toby cabot wrote:
On Mon, Jan 24, 2005 at 04:56:35PM -0500, toby cabot wrote:I have a problem at run-time with Xerces inside a web app that appears to be classloader related. I'm using Axis which uses Xerces so I added the xerces jars to my .war file. When Xerces starts I get:
java.lang.ClassCastException
I'm still not certain what's going on, but I have some clues. The "old" version of Geronimo (i.e. early January) loads Axis from the jars in my .war file, but the new version loads Axis from the jars in the geronimo repository. This seems to cause a problem when Axis then loads Xerces from the jars in my war file.
Is there a way that I can get the old behavior, i.e. have Geronimo use the version of Axis that's packaged in my war file?
Thanks, Toby
