It's not using the xerces.jar from WAS
- first, if I remove my version of xerces from the classpath, SOAP stops working
- secondly: I tried to replace the WAS xerces.jar with my version, and got the same error.
So that is unfortunately not the problem.
Michael
Steve D George wrote:
Hi Michael, I've seen errors similar to this when using websphere in the past but not specifically when using SOAP. They have usually been down to the fact that a non compatible version of xerces is being found. Websphere has a hierarchy of classloaders and I'm guessing that the class that is being picked up is probably in one of the xerces JARs that ships with WAS rather than in your Xerces 2.4 jar.
Hope that helps,
Steve.
