Yes please with sample code/wsdl/schema to recreate the problem.
thanks, dims On 2/2/07, Javier Kohen <[EMAIL PROTECTED]> wrote:
El mié, 31-01-2007 a las 20:23 -0800, footh escribió: > I am using the above asynchronous call to invoke a web > service with a Callback class. > > When the request causes a SOAPFault, the onError > method of the Callback class is called. However, it > seems to be called with an empty exception. I have no > way of retrieving the SOAP Fault xml text. > > I know the invocation is returning a response because > I can see it in the console with debugging on. > > Is there any way to retrieve the SOAP Fault xml using > this method of invoking a web service? I saw the same problem, but it turned out that due to an error I made in the WSDL (I have no control on the remote server), it was caused by the fact that Axis didn't recognize the fault message. I crafted a simple example and used the axis2server to test it, and the issue was solved. HOWEVER, I'm faced with a different, related issue now. When using async. calls Axis passes an AxisFault object to the handleError method instead of the actual exception corresponding to the fault. The AxisFault object allows one to retrieve the OMElements that compose the details, but if I'm using bindings (XMLbindings in my case), I expect to be able to use those instead of having to write the code by hand. Moreover, when using sync. calls, the exception is used, so I'm pretty sure that this is a bug. Should I open a JIRA? I'm using Axis2 1.1.1. Thanks, -- Javier Kohen <[EMAIL PROTECTED]> ICQ: blashyrkh #2361802 Jabber: [EMAIL PROTECTED]
-- Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
