I solved my problem.
I missed putting xerces.jar into WebSphere\AppServer\bin\admin.config.
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 compat
How did you configure WAS to pick up Xerces? Did you follow the directions at
http://cvs.apache.org/viewcvs.cgi/*checkout*/ws-soap/java/docs/install/websphere.html?rev=1.6?
Scott Nichol
Do not send e-mail directly to this e-mail address,
because it is filtered to accept only mail from
specific
: Tuesday, December 16, 2003 7:28 AM
Subject: Re: RPCRouter install problem
> Hi,
>
> 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 vers
Hi,
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
XercesImpl.jar version is incorrect
Updating your JAR may harm WAS..what does IBM support say?
-Martin
- Original Message -
From: "Michael Hansen, Presys A/S" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, December 16, 2003 6:15 AM
Subject: RPCRouter install problem
> I am ha
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
b
