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 "Deepal Jayasinghe (JIRA)" <ji...@apache.org> on 2005/08/11 14:49:00 UTC

[jira] Commented: (AXIS2-136) HTTP 500 status not set when a SOAP fault is thrown and not accepted by the Client API

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

Deepal Jayasinghe commented on AXIS2-136:
-----------------------------------------

fixed the bug but not in the correct way
the correct way should be when an error get at the client side it is required to call engine.recieveFault() rather than throwing exception. I will fix that latter in next release


> HTTP 500 status not set when a SOAP fault is thrown and not accepted by the Client API
> --------------------------------------------------------------------------------------
>
>          Key: AXIS2-136
>          URL: http://issues.apache.org/jira/browse/AXIS2-136
>      Project: Apache Axis 2.0 (Axis2)
>         Type: Bug
>   Components: transports
>     Versions: 0.91
>     Reporter: Ruchith Udayanga Fernando
>     Assignee: Deepal Jayasinghe
>      Fix For: 0.91

>
> Seems like we are not setting HTTP 500 when Axis2 throws a SOAP Fault
> Ref:
> http://www.w3.org/TR/2003/REC-soap12-part0-20030624/#L26866
> "If an error occurs processing the request, the HTTP binding specification requires that a HTTP 500 "Internal Server Error" be used with an embedded SOAP message containing a SOAP fault indicating the server-side processing error."
> http://www.w3.org/TR/2003/REC-soap12-part0-20030624/#Example10

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