[jira] Resolved: (AXIS2-113) Client side exception handling

["Eran Chinthaka (JIRA)" <ji...@apache.org>]

     [ http://issues.apache.org/jira/browse/AXIS2-113?page=all ]
     
Eran Chinthaka resolved AXIS2-113:
----------------------------------

    Resolution: Fixed

Sorry for adding a wrong comment. The feature is as follows;

With the earlier code, if there is a SOAP fault, client will get a Java Exception which contains either the stacktrace recd from the server side or the fault reason, if the stacktrace is not available.
This hinders user's ability to access the incoming fault SOAP message. THe above falg will enable that.

I fixed this and committed the code.

> Client side exception handling
> ------------------------------
>
>          Key: AXIS2-113
>          URL: http://issues.apache.org/jira/browse/AXIS2-113
>      Project: Apache Axis 2.0 (Axis2)
>         Type: New Feature
>   Components: client-api
>     Reporter: Eran Chinthaka
>     Assignee: Eran Chinthaka
>     Priority: Minor

>
> In the client side, if the recd SOAP message contains a SOAP fault, we throw an exception to the application with the information extracted from the Fault message.
> But sometimes, due to security reasons sending fault information to the application is not desirable. And some times it may be required to get the recd SOAP message, with the fault, as it is.
> So better to have a flag in the MEPClient, either to get the java exception or the soap message.

-- 
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