[ http://issues.apache.org/jira/browse/AXIS2-917?page=comments#action_12428724 ] Derek Foster commented on AXIS2-917: ------------------------------------
It seems that the discussion in this bug report has gotten somewhat far away from the original problem that the bug report was reporting. I suggest opening up an additional JIRA entry to handle any specific deficiency in Axis2's implementation of (as opposed to interface to) fault handling, rather than discussing it here. I created *this* bug report to report the fact that the existing fault handling support is undocumented, and as a result, it is not at all clear how it is even *supposed* to be used. Note that this specific bug is logged against the documentation, not the Axis implementation. Whether Axis2's fault handling works *correctly* or not is an entirely different question, and should be handled in its own bug report. (Please do provide a link to it here, however.) Anyway, with that understanding, I would like to request that this JIRA entry be listed as a blocker for Axis2 1.1. I think that having the expected usage of fault handling be clearly documented is essential towards using Axis2 for any nontrivial application, and I think that the user guide absolutely needs to describe clearly how it is supposed to be done and provide a working example. Actually, this should have been provided in the Axis2 1.0 documentation, I think, and the repeated questions on the mailing list about it demonstrate how much it is needed. > 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: Critical > Attachments: 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
