ws-soap-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Scott Nichol" <>
Subject Re: Migrating from Apache SOAP to Axis
Date Wed, 13 Oct 2004 16:38:15 GMT
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

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 ----- 
From: "Shukla, Minaxi" <>
To: <>
Sent: Wednesday, October 13, 2004 11:58 AM
Subject: Migrating from Apache SOAP to Axis


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 '' using encoding
style 'null'.

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

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.)


View raw message