axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eran Chinthaka (JIRA)" <>
Subject [jira] Resolved: (AXIS2-917) User guide should give explanation and examples of fault handling
Date Mon, 02 Oct 2006 10:23:20 GMT
     [ ]

Eran Chinthaka resolved AXIS2-917.

    Fix Version/s: 1.1
       Resolution: Fixed

Samples added to Axis2. 

> User guide should give explanation and examples of fault handling
> -----------------------------------------------------------------
>                 Key: AXIS2-917
>                 URL:
>             Project: Apache Axis 2.0 (Axis2)
>          Issue Type: Wish
>          Components: samples, build,site  & docs
>    Affects Versions: 1.0
>            Reporter: Derek Foster
>         Assigned To: Eran Chinthaka
>            Priority: Blocker
>             Fix For: 1.1
>         Attachments: axis2-917-example-2nd-attempt.jar, axis2-917-example.jar, sampleService-wsdl.rar
> The Axis2 user guide provides no examples of:
>   1) The WSDL to declare that a fault may be thrown from an operation (suitable for passing
into WSDL2Java)
>   2) The server-side code for a fault exception, as generated by WSDL2Java and modified
as a user might be expected to modify it.
>   3) The server-side code to throw the fault exception, including a tested example of
passing on a custom error message to be transmitted as part of a SOAP fault (in the faultDetail)
and received by the client.
>   4) The client-side code for receiving and handling a fault.
> Furthermore, what discussion of faults that there is seems fairly contradictory. For
instance, there are various suggestions that throwing an AxisFault exception from a service
is the way to issue a fault. However, WSDL2Java does not generate service methods that are
declared to throw AxisFault, and there seems to be no way to declare such a fault in WSDL.
(at least, none that I can find). Fault generation from a service that was not generated by
WSDL2Java should be treated as a separate section, since it is handled in a totally different
manner by server code. I think that both kinds of fault handling need to be documented clearly
in the user guide.
> I have been trying for weeks to figure out how this is supposed to work, and still haven't
gotten it to work quite right (my custom error message included in the thrown fault exception
is getting lost somewhere before the SOAP fault is transmitted). This is a basic feature that
should be documented clearly.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message