axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zhuojian Georgia Han \(zhuhan\)" <>
Subject RE: Why SOAP FAULT does not convert into AxisFault
Date Wed, 19 Sep 2007 21:11:52 GMT
Thanks for the reply. Which version of Axis support SOAP1.2?


From: Anne Thomas Manes [] 
Sent: Wednesday, September 19, 2007 1:45 PM
Subject: Re: Why SOAP FAULT does not convert into AxisFault

You want to use the Robust One-Way message exchange pattern -- available
with SOAP 1.2.

On 9/19/07, Zhuojian Georgia Han (zhuhan) <
<> > wrote: 

	I resolved this problem. The reason exception did not raised by
client is that this function does not have return parameters, so in Axis
stub it translates into an one-way invoke call. That's why even if the
server sends back the soap fault, the client doesn't process the result.

	I can understand that in one-way call the client does ignore the
server response. but in case of there is a soap fault, client should not
ignore it. Maybe function should not translate into one-way call even
there is no return parameter.

	From: Zhuojian Georgia Han (zhuhan) 
	Sent: Tuesday, September 18, 2007 2:27 PM
	Subject: Why SOAP FAULT does not convert into AxisFault
	I use gSoap in server side, and Java Axis as my Soap client.
When gSoap raise   a soap fault, it seems like Axis Soap doesn't convert
into AxisFault, in Axis client side, it doesn't go to AxisFault
Exception or generic Exception catch block, why is that? I'm using Axis
1.4, and I remember it used to work on Axis1.2. 
	 I can not see anything wrong in this soapfault message,   any
special field which is needed to be set in soapfault?  Is  this  an
Axis1.4 bug?
	Below are soapfault packet which I captured in ethereal.

View raw message