Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@ws.apache.org
Message-ID: <10985346.1159314410759.JavaMail.jira@brutus>
Date: Tue, 26 Sep 2006 16:46:50 -0700 (PDT)
From: "William Ferguson (JIRA)" <jira@apache.org>
To: axis-dev@ws.apache.org
Subject: [jira] Commented: (AXIS2-917) User guide should give explanation
 and examples of fault handling
In-Reply-To: <7353237.1153506373834.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

    [ http://issues.apache.org/jira/browse/AXIS2-917?page=comments#action_12437971 ] 
            
William Ferguson commented on AXIS2-917:
----------------------------------------

Changing #2 and #3 as I have indicated will have little or no impact on existing code.

#2 if the stub data handlers are regenerated from the WSDL then they will still work ok. If they are not then they will cntinue to extend from RemoteException which itself extedns from Exception, so no client code will need to change.

#3 If the stub constructor throws AxisFault instead of Exception then again no client code needs to change as all existing client code will have to be catching Exception. AxisFault is just a narrow of that Exception.

In both cases, future code can be better but existing code need not change.

> User guide should give explanation and examples of fault handling
> -----------------------------------------------------------------
>
>                 Key: AXIS2-917
>                 URL: http://issues.apache.org/jira/browse/AXIS2-917
>             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
>         Attachments: 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: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org