We are using the standard parser, however, we have a customized version of SOAP based on 2.0 that we need to use. If the xerces parser that ships with Websphere 4.0 is visible by all ear files then we should be OK. Are there compatibility issues with the xerces parser that ships with Websphere 4.0 and SOAP 2.0? The version they are shipping is more than likely newer than what we are shipping with our product (1.1.3). I am not aware of any limitation with newer version of the parser.
Bill
-----Original Message-----
From: Keith Wells [SMTP:[EMAIL PROTECTED]]
Sent: Wednesday, September 26, 2001 8:03 AM
To: [EMAIL PROTECTED]
Subject: Re: Websphere 4.0
Bill,
Are you using the xerces that comes with WAS 4.0 or did you package your
own version of xerces in your ear file?
Keith Wells
>>Anyone tried getting SOAP running on this platform.� We have applications
based on SOAP 2.0 that we are trying to get running on Websphere 4.0 and
are having little >>luck.� It appears that there is a classpath problem and
it is not finding xerces.jar since we are getting parser errors indicative
of this error.� We have not been able to find >>anything on how to set the
classpath such that for our container (ear file??) has a proper class path.
Any info appreciated.
>>Regards,
>>Bill
