Mailing-List: contact soap-user-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: soap-user@ws.apache.org
Received-SPF: pass (hermes.apache.org: local policy)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Migrating from Apache SOAP to Axis
Date: Wed, 13 Oct 2004 17:57:41 -0500
Message-ID: 
 <8A1F9FA924FBDB47A53086AA86BBDDA396B3FC@sgtulmsp03.global.ad.sabre.com>
Thread-Topic: Migrating from Apache SOAP to Axis
Thread-Index: AcSxYcPgTs4WFcEGR0moN7ofaC/YhQAFcdZA
From: "Shukla, Minaxi" <Minaxi.Shukla@sabre-holdings.com>
To: <soap-user@ws.apache.org>

Scott,

Both captures has response with Fault.

The first part is the request message and after that there is response =
message.

Let me know if you need more info.

Thanks

-Minaxi

 -----Original Message-----
From: 	Scott Nichol [mailto:snicholnews@scottnichol.com]=20
Sent:	Wednesday, October 13, 2004 3:22 PM
To:	soap-user@ws.apache.org
Subject:	Re: Migrating from Apache SOAP to Axis

Do you have a capture when the Axis service returns a Fault?

Scott Nichol

Do not send e-mail directly to this e-mail address,
because it is filtered to accept only mail from
specific mail lists.
----- Original Message -----=20
From: "Shukla, Minaxi" <Minaxi.Shukla@sabre-holdings.com>
To: <soap-user@ws.apache.org>
Sent: Wednesday, October 13, 2004 12:54 PM
Subject: RE: Migrating from Apache SOAP to Axis


Yes, I have captured the SOAP messages from both the deployments (with =
Apache SOAP and Axis). See the SOAP messages attached.

Thanks for your help

-Minaxi
 <<routeApacheSOAP.txt>>  <<routeAxis.txt>>=20


 -----Original Message-----
From: Scott Nichol [mailto:snicholnews@scottnichol.com]=20
Sent: Wednesday, October 13, 2004 11:38 AM
To: soap-user@ws.apache.org
Subject: Re: Migrating from Apache SOAP to Axis

What would help most: capture and post to this list the contents of the =
response that is causing the client a problem.  Depending on your OS and =
tool preference, you can capture with Network Monitor (Windows), tcpdump =
(*nix), TcpTunnelGui (Apache SOAP), tcpmon (Axis), tcpTrace/proxyTrace =
(for Windows at www.simonfell.com).

Scott Nichol

Do not send e-mail directly to this e-mail address,
because it is filtered to accept only mail from
specific mail lists.

----- Original Message -----=20
From: "Shukla, Minaxi" <Minaxi.Shukla@sabre-holdings.com>
To: <soap-user@ws.apache.org>
Sent: Wednesday, October 13, 2004 11:58 AM
Subject: Migrating from Apache SOAP to Axis


Hi,

I want to migrate our web services deployed on Apache SOAP 2.2 to Axis =
1.1 without having to update the client developed with Apache SOAP.

It works fine with good scenarios where the service returns a successful =
respose. But, when service throws a business exception, the client gets =
ClassCastException :

java.lang.ClassCastException : =
org.apache.xerces.dom.DeferredElementNSImpl

I looked into Apache SOAP source code and found that the detailEntry is =
not deserialized because of missing encoding style in the response. I =
added a line to print the exception in Fault class unmarshall() method =
(the catch Exception block):

Exception while unmarshalling Fault : =
java.lang.IllegalArgumentException: No Deserializer found to deserialize =
a 'http://schemas.xmlsoap.org/soap/envelope/:Parameter' using encoding =
style 'null'.

So, looks like Axis is not returning the encodingStyle in response. I =
don't know how to fix that.

Attached is the deployment descriptor for the service.

Thanks in advance for any help.

(I will post this message on Axis user list also, but I saw a message on =
this list regarding SOAP to Axis migration, so just want to see if =
anyone can help.)

-Minaxi
 <<GeoRoute.wsdd>>=20