You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-user@xml.apache.org by st...@foretek.com on 2000/12/11 15:47:24 UTC

SOAP & Websphere

Hi All -- I'm trying to determine what level of support IBM's WebSphere has for
SOAP.  I'm drawing a blank looking through various online resources.  Can anyone
point me at some references to this?

Thanks,
-Steve.

Re: SOAP & Websphere

Posted by Cory Isaacson <ci...@capita2.com>.
Steve,

There isn't much online, but I have gotten it running with WS 3.02. You need
to do the following:

A) Upgrade to JDK1.1.8
B) Make your own version of RPCRouterServlet which changes the
'session.setAttribute' calls to 'session.setValue' as WS 3.02 uses the older
version of the Servlet JDK. The newest release of WS 3.5 should make this
unnecessary.

Once this is done, you can add the required Xerces.jar 1.1.3 to your
admin.config classpath, and move the Xml4j.jar to the end of the classpath
(i.e., after Xerces.jar). Create an application, add soap.jar in the
classpath, and configure the RPCRouterServlet in the application.

That should get you going. It works fine once you have it configured
properly.

Thanks,

Cory
----- Original Message -----
From: <st...@foretek.com>
To: <so...@xml.apache.org>
Sent: Monday, December 11, 2000 6:47 AM
Subject: SOAP & Websphere


> Hi All -- I'm trying to determine what level of support IBM's WebSphere
has for
> SOAP.  I'm drawing a blank looking through various online resources.  Can
anyone
> point me at some references to this?
>
> Thanks,
> -Steve.
>
>

Re: SOAP & Websphere

Posted by Cory Isaacson <ci...@capita2.com>.
Steve,

There isn't much online, but I have gotten it running with WS 3.02. You need
to do the following:

A) Upgrade to JDK1.1.8
B) Make your own version of RPCRouterServlet which changes the
'session.setAttribute' calls to 'session.setValue' as WS 3.02 uses the older
version of the Servlet JDK. The newest release of WS 3.5 should make this
unnecessary.

Once this is done, you can add the required Xerces.jar 1.1.3 to your
admin.config classpath, and move the Xml4j.jar to the end of the classpath
(i.e., after Xerces.jar). Create an application, add soap.jar in the
classpath, and configure the RPCRouterServlet in the application.

That should get you going. It works fine once you have it configured
properly.

Thanks,

Cory
----- Original Message -----
From: <st...@foretek.com>
To: <so...@xml.apache.org>
Sent: Monday, December 11, 2000 6:47 AM
Subject: SOAP & Websphere


> Hi All -- I'm trying to determine what level of support IBM's WebSphere
has for
> SOAP.  I'm drawing a blank looking through various online resources.  Can
anyone
> point me at some references to this?
>
> Thanks,
> -Steve.
>
>