ws-soap-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ara Kassabian" <>
Subject RE: Using SOAP with Websphere
Date Tue, 18 Jul 2000 23:59:04 GMT
Our experience with WebLogic indicates that you need to either upgrade to
JSP 1.1 somehow or patch the SOAP JSP pages as indicated by Wouter.

Ara Kassabian
TechOne, Inc.
100 N. Brand Blvd., Suite 605
Glendale, CA 91203
(510) 729-6750 Ext. 396 (Oakland)
(818) 476-0055 (Los Angeles)

-----Original Message-----
From: Cory Isaacson []
Sent: Tuesday, July 18, 2000 4:38 PM
Subject: Fw: Using SOAP with Websphere


Thanks for this info. We are using WebSphere 3.02, with JDK1.1.7, which
supports JSP1.0. Do we still have to do the patch you talk about in #1?

Also, did you install the SOAP Servlets in a web application?

If you fill in these couple of blanks, I think we'll be all set. I am also
willing to do a complete set of instructions if you can help me get it up
and running.


----- Original Message -----
From: "Wouter Cloetens" <>
To: <>
Cc: "Guy Galil" <>
Sent: Tuesday, July 18, 2000 5:12 AM
Subject: Re: Using SOAP with Websphere

> On Sun, 16 Jul 2000 11:14:05 +0200, Guy Galil wrote:
> >We use IBM WebSphere 2.03
> >What do we need to do to run the SOAP server under it instead of
> Guy,
> I've been running the IBM SOAP4j for a while on WebSphere now. I
Sanjiva to
> write up the instructions properly so he could include it in the FAQ
but I can't find the
> time to do it. I'm going to dump a quick & dirty in here and I hope it
helps you. I will forward
> all the files I patched to you privately (note: all still SOAP4j level).
> What I did:
> 1. Patched SOAPMappingRegistry to make it work on JDK 1.1.6. See my post
dated 29
> May on the alphaworks discussion forum. This still isn't fixed in the
latest version of that
> file in Apache-SOAP.
> 2. Ported the deployment tool and RPC routing JSP files to a level
understood by
> WebSphere v2 (JSP version 0.9 or 0.91 I think?). I took the easy
and ripped out
> support for anything but the "request" scope.
> 3. Put xerces.jar in the WebSphere JVM classpath before xml4j.jar (use
> interface to access the JVM settings, or edit
> bfn, Wouter

View raw message