You are viewing a plain text version of this content. The canonical link for it is here.

Posted to java-dev@axis.apache.org by "Eran Chinthaka (JIRA)" <ji...@apache.org> on 2005/08/01 03:48:35 UTC

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

    [ http://issues.apache.org/jira/browse/AXIS2-113?page=comments#action_12317270 ] 

Eran Chinthaka commented on AXIS2-113:
--------------------------------------

Fixed this.

Added a flag and set method in MEPClient and put the code in InOutMEPClient.

Please can someone resolve this issue.

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