You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-dev@xml.apache.org by Wouter Cloetens <wc...@raleigh.ibm.com> on 2000/10/28 21:29:50 UTC
Re: SOAP 2.0 and WebSphere 3.5
Scott,
It looks fairly simple. JDSK 2.2 deprecates HttpSession.{get|set}Value()
in favour of the new {get|set}Attribute() methods. All I did was change the
2 xetAttribute references to xetValue in ServerHTTPUtils.java to make
things work on WebSphere 3.0.2.2.
It raises a question about Apache-SOAP's strategy with regards to
backward compatibility. Outside Tomcat, I don't think there are many
servlet engines that implement JDSK 2.2. Should we stick with deprecated
methods for a while, or stay on the bleeding edge and force everybody
who doesn't use the latest & greatest to patch the source?
--- xml-soap/java/src/org/apache/soap/server/http/ServerHTTPUtils.java Mon Oct 23 14:15:00 2000
+++ xml-soap-jsdk21/java/src/org/apache/soap/server/http/ServerHTTPUtils.java Sun Oct 29 00:24:08 2000
@@ -205,7 +205,7 @@
// locate (or create) the target object and invoke the method
synchronized (scopeLock) {
if (scopeLock == session) {
- targetObject = session.getAttribute (targetID);
+ targetObject = session.getValue (targetID);
} else if (scopeLock == context) {
targetObject = context.getAttribute (targetID);
} else {
@@ -236,7 +236,7 @@
// in that case the object is to be thrown away after handling
// the request
if (scopeLock == session) {
- session.setAttribute (targetID, targetObject);
+ session.setValue (targetID, targetObject);
} else if (scopeLock == context) {
context.setAttribute (targetID, targetObject);
}
bfn, Wouter
On Tue, 24 Oct 2000 15:52:18 -0500, sgerard@us.ibm.com wrote:
>I've been having a lot of trouble trying to get SOAP 2.0 running on
>WebSphere 3.5. I've finally tracked down the problem. SOAP 2.0 requires
>Servlet API 2.2, but WebSphere 3.5 only support Servlet API 2.1.1. So,
>
> SOAP 2.0 does not run on WebSphere 3.5.
>
>I found this when I tried to compile the RPCRouterServlet and got compile
>errors. Hopefully, WebSphere fix pack 2 will fix this problem.
>
>Scott Gerard,
>IBMUSM07(sgerard)
>Dept. DXS
>Phone 507-253-7896 Tie 553-7896
>Mail on Lotus Notes: Scott Gerard/Rochester/IBM
>Mail from the Internet: sgerard@us.ibm.com
>
--
http://www.workspot.net/~zombie/soap/
My opinions are irrelevant. They will be assimilated by my employer.
Re: SOAP 2.0 and WebSphere 3.5
Posted by Cory Isaacson <ci...@capita2.com>.
I suggested this months ago as well, but most people rejected it as they
wanted the newer version. I agree that many servlet engines will not handle
this.
Cory
----- Original Message -----
From: "Wouter Cloetens" <wc...@raleigh.ibm.com>
To: <sg...@us.ibm.com>; <so...@xml.apache.org>
Cc: <so...@xml.apache.org>
Sent: Saturday, October 28, 2000 2:29 PM
Subject: Re: SOAP 2.0 and WebSphere 3.5
> Scott,
>
> It looks fairly simple. JDSK 2.2 deprecates HttpSession.{get|set}Value()
> in favour of the new {get|set}Attribute() methods. All I did was change
the
> 2 xetAttribute references to xetValue in ServerHTTPUtils.java to make
> things work on WebSphere 3.0.2.2.
>
> It raises a question about Apache-SOAP's strategy with regards to
> backward compatibility. Outside Tomcat, I don't think there are many
> servlet engines that implement JDSK 2.2. Should we stick with deprecated
> methods for a while, or stay on the bleeding edge and force everybody
> who doesn't use the latest & greatest to patch the source?
>
> --- xml-soap/java/src/org/apache/soap/server/http/ServerHTTPUtils.java Mon
Oct 23 14:15:00 2000
> +++
xml-soap-jsdk21/java/src/org/apache/soap/server/http/ServerHTTPUtils.java
Sun Oct 29 00:24:08 2000
> @@ -205,7 +205,7 @@
> // locate (or create) the target object and invoke the method
> synchronized (scopeLock) {
> if (scopeLock == session) {
> - targetObject = session.getAttribute (targetID);
> + targetObject = session.getValue (targetID);
> } else if (scopeLock == context) {
> targetObject = context.getAttribute (targetID);
> } else {
> @@ -236,7 +236,7 @@
> // in that case the object is to be thrown away after handling
> // the request
> if (scopeLock == session) {
> - session.setAttribute (targetID, targetObject);
> + session.setValue (targetID, targetObject);
> } else if (scopeLock == context) {
> context.setAttribute (targetID, targetObject);
> }
>
>
> bfn, Wouter
>
> On Tue, 24 Oct 2000 15:52:18 -0500, sgerard@us.ibm.com wrote:
>
> >I've been having a lot of trouble trying to get SOAP 2.0 running on
> >WebSphere 3.5. I've finally tracked down the problem. SOAP 2.0 requires
> >Servlet API 2.2, but WebSphere 3.5 only support Servlet API 2.1.1. So,
> >
> > SOAP 2.0 does not run on WebSphere 3.5.
> >
> >I found this when I tried to compile the RPCRouterServlet and got compile
> >errors. Hopefully, WebSphere fix pack 2 will fix this problem.
> >
> >Scott Gerard,
> >IBMUSM07(sgerard)
> >Dept. DXS
> >Phone 507-253-7896 Tie 553-7896
> >Mail on Lotus Notes: Scott Gerard/Rochester/IBM
> >Mail from the Internet: sgerard@us.ibm.com
> >
>
> --
> http://www.workspot.net/~zombie/soap/
> My opinions are irrelevant. They will be assimilated by my employer.
>
Re: SOAP 2.0 and WebSphere 3.5
Posted by Cory Isaacson <ci...@capita2.com>.
I suggested this months ago as well, but most people rejected it as they
wanted the newer version. I agree that many servlet engines will not handle
this.
Cory
----- Original Message -----
From: "Wouter Cloetens" <wc...@raleigh.ibm.com>
To: <sg...@us.ibm.com>; <so...@xml.apache.org>
Cc: <so...@xml.apache.org>
Sent: Saturday, October 28, 2000 2:29 PM
Subject: Re: SOAP 2.0 and WebSphere 3.5
> Scott,
>
> It looks fairly simple. JDSK 2.2 deprecates HttpSession.{get|set}Value()
> in favour of the new {get|set}Attribute() methods. All I did was change
the
> 2 xetAttribute references to xetValue in ServerHTTPUtils.java to make
> things work on WebSphere 3.0.2.2.
>
> It raises a question about Apache-SOAP's strategy with regards to
> backward compatibility. Outside Tomcat, I don't think there are many
> servlet engines that implement JDSK 2.2. Should we stick with deprecated
> methods for a while, or stay on the bleeding edge and force everybody
> who doesn't use the latest & greatest to patch the source?
>
> --- xml-soap/java/src/org/apache/soap/server/http/ServerHTTPUtils.java Mon
Oct 23 14:15:00 2000
> +++
xml-soap-jsdk21/java/src/org/apache/soap/server/http/ServerHTTPUtils.java
Sun Oct 29 00:24:08 2000
> @@ -205,7 +205,7 @@
> // locate (or create) the target object and invoke the method
> synchronized (scopeLock) {
> if (scopeLock == session) {
> - targetObject = session.getAttribute (targetID);
> + targetObject = session.getValue (targetID);
> } else if (scopeLock == context) {
> targetObject = context.getAttribute (targetID);
> } else {
> @@ -236,7 +236,7 @@
> // in that case the object is to be thrown away after handling
> // the request
> if (scopeLock == session) {
> - session.setAttribute (targetID, targetObject);
> + session.setValue (targetID, targetObject);
> } else if (scopeLock == context) {
> context.setAttribute (targetID, targetObject);
> }
>
>
> bfn, Wouter
>
> On Tue, 24 Oct 2000 15:52:18 -0500, sgerard@us.ibm.com wrote:
>
> >I've been having a lot of trouble trying to get SOAP 2.0 running on
> >WebSphere 3.5. I've finally tracked down the problem. SOAP 2.0 requires
> >Servlet API 2.2, but WebSphere 3.5 only support Servlet API 2.1.1. So,
> >
> > SOAP 2.0 does not run on WebSphere 3.5.
> >
> >I found this when I tried to compile the RPCRouterServlet and got compile
> >errors. Hopefully, WebSphere fix pack 2 will fix this problem.
> >
> >Scott Gerard,
> >IBMUSM07(sgerard)
> >Dept. DXS
> >Phone 507-253-7896 Tie 553-7896
> >Mail on Lotus Notes: Scott Gerard/Rochester/IBM
> >Mail from the Internet: sgerard@us.ibm.com
> >
>
> --
> http://www.workspot.net/~zombie/soap/
> My opinions are irrelevant. They will be assimilated by my employer.
>