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 "Gopalakrishnan (JIRA)" <ji...@apache.org> on 2005/07/26 09:25:18 UTC

[jira] Created: (AXIS2-98) InOutMEPClient.invokeBlocking() can not expect to have a Exception element in a Fault message

InOutMEPClient.invokeBlocking() can not expect to have a Exception element in a Fault message
---------------------------------------------------------------------------------------------

         Key: AXIS2-98
         URL: http://issues.apache.org/jira/browse/AXIS2-98
     Project: Apache Axis 2.0 (Axis2)
        Type: Improvement
  Components: client-api  
    Versions: 0.9    
    Reporter: Gopalakrishnan


The fault handling code in InOutMEPClient.invokeBlocking() looks like this:
 if (resenvelope.getBody().hasFault()) {
           throw new AxisFault(resenvelope.getBody().getFault().getException());
  }

But how can we expect to have an Exception element in the details element of a soap fault, always?
So when we get a SOAP Fualt withought an exception element, the Call throws an Axisfault with the message 

org.apache.axis2.engine.AxisFault: No Exception element found in the SOAP Detail element; nested exception is:
java.lang.Exception: No Exception element found in the SOAP Detail element
at org.apache.axis2.clientapi.InOutMEPClient.invokeBlocking(InOutMEPClient.java:159)
at org.apache.axis2.clientapi.Call.invokeBlocking(Call.java:95)

which is of no use. It doesn't tell me any thing about the acatual fault recieved.

It will be better if InOutMEPClient.invokeBlocking()  throws an AxisFault with the content of the Fault detail element.

Also the AxisFault does contain the faulCode, subCode, reason etc. of the SOAPFault message recieved!

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


[jira] Resolved: (AXIS2-98) InOutMEPClient.invokeBlocking() can not expect to have a Exception element in a Fault message

Posted by "Srinath Perera (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/AXIS2-98?page=all ]
     
Srinath Perera resolved AXIS2-98:
---------------------------------

    Resolution: Fixed

Fixed

> InOutMEPClient.invokeBlocking() can not expect to have a Exception element in a Fault message
> ---------------------------------------------------------------------------------------------
>
>          Key: AXIS2-98
>          URL: http://issues.apache.org/jira/browse/AXIS2-98
>      Project: Apache Axis 2.0 (Axis2)
>         Type: Improvement
>   Components: client-api
>     Versions: 0.9
>     Reporter: Gopalakrishnan

>
> The fault handling code in InOutMEPClient.invokeBlocking() looks like this:
>  if (resenvelope.getBody().hasFault()) {
>            throw new AxisFault(resenvelope.getBody().getFault().getException());
>   }
> But how can we expect to have an Exception element in the details element of a soap fault, always?
> So when we get a SOAP Fualt withought an exception element, the Call throws an Axisfault with the message 
> org.apache.axis2.engine.AxisFault: No Exception element found in the SOAP Detail element; nested exception is:
> java.lang.Exception: No Exception element found in the SOAP Detail element
> at org.apache.axis2.clientapi.InOutMEPClient.invokeBlocking(InOutMEPClient.java:159)
> at org.apache.axis2.clientapi.Call.invokeBlocking(Call.java:95)
> which is of no use. It doesn't tell me any thing about the acatual fault recieved.
> It will be better if InOutMEPClient.invokeBlocking()  throws an AxisFault with the content of the Fault detail element.
> Also the AxisFault does contain the faulCode, subCode, reason etc. of the SOAPFault message recieved!

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