RE: [soapbuilders] interop: Exception Handling between Axis Server + gSOAP Client
- This is a question better suited for the Axis mailing lists.
Axis does support mapping faults in to typed exceptions and does so my
mapping the element in the <detail> element on to an Exception type.
I am unclear from your description what exactly the situation you are
running in to. Axis will probably not serialize any member variable of
the exception that starts with "__". It should serialize any part of
the Exception class that it describes in the WSDL however.
In any case, you should send your question to the axis-user list.
From: email@example.com [mailto:firstname.lastname@example.org]
On Behalf Of stef_binder
Sent: Wednesday, April 20, 2005 2:50 AM
Subject: [soapbuilders] interop: Exception Handling between Axis Server
+ gSOAP Client
i am implementing a ws-client with gSOAP Toolkit to consume a WS on an
Axis Server (1.2rc1).
I have no problem with normal usage, but with exceptions thrown by the
in the WSDL are 5 Exception-Classes, but generatet FAULT object only
includes the error-code of the exception (errorcode element is common
to all exception classes) in the _detail->any field.
(soap_print_fault writes this:
SOAP FAULT: SOAP-ENV:Server.generalException
the "__type" member of Fault is always 0, and the "fault" member is
Does anybody know how to deal with this?
as the errorcodes always start at 0, and some functions can throw all
different exceptions, it is meaningless for me, when i dont know the
I´ve read here:
http://www.gridlab.org/WorkPackages/wp-5/guide/faults.html that axis
dont give back typed exceptions.
theres a little workaround, but only for pure C clients and not
working with more than one exception-class.
Any help is greatly appreciated! (time for project is getting short ;) )
This group is a forum for builders of SOAP implementations to discuss
implementation and interoperability issues. Please stay on-topic.
Yahoo! Groups Links