ws-soap-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ara Kassabian" <...@techone.com>
Subject Using SOAP with WebLogic
Date Tue, 18 Jul 2000 20:35:21 GMT
I was also able to make SOAP run with WebLogic 5.1 with only one change:

The undeploy.jsp file needed to be renamed to _undeploy.jsp. The reason is
that the code generated by the JSP compiler includes a string like "file:
myserver\public_html\SOAP\undeploy.jsp". Unfortunately, the \u gets
interpreted as an escaped string by the Java compiler. This causes a
compile-time error to be thrown.

Note that the JSP files will not run under WebLogic 4.5.1, as they
apparently require a JSP 1.1 compiler (and WL 4.5.1 is only JSP 1.0).

----------------------------------------------
Ara Kassabian
TechOne, Inc.
100 N. Brand Blvd., Suite 605
Glendale, CA 91203
http://www.techone.com
ara@techone.com
(510) 729-6750 Ext. 396 (Oakland)
(818) 476-0055 (Los Angeles)

-----Original Message-----
From: Wouter Cloetens [mailto:wcloeten@raleigh.ibm.com]
Sent: Tuesday, July 18, 2000 2:12 AM
To: soap-user@xml.apache.org
Cc: Guy Galil
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 Tomcat.

Guy,

I've been running the IBM SOAP4j for a while on WebSphere now. I promised
Sanjiva to
write up the instructions properly so he could include it in the FAQ list,
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 approach
and ripped out
support for anything but the "request" scope.
3. Put xerces.jar in the WebSphere JVM classpath before xml4j.jar (use the
admin
interface to access the JVM settings, or edit
properties/bootstrap.properties).

bfn, Wouter



Mime
View raw message