[ http://issues.apache.org/jira/browse/AXIS2-345?page=all ]
Ruchith Udayanga Fernando resolved AXIS2-345:
---------------------------------------------
Resolution: Fixed
This is fixed in ServiceClient.sendRobust(OMElement elem) throws AxisFault
> InOnly MEP should rethrow transport level exceptions
> ----------------------------------------------------
>
> Key: AXIS2-345
> URL: http://issues.apache.org/jira/browse/AXIS2-345
> Project: Apache Axis 2.0 (Axis2)
> Type: Bug
> Components: core
> Reporter: Peter McEvoy
>
> After a series of emails on axis-users, it was recommended [1] that I log an
> issue here.
> The in-only MEP should rethrow transport level exceptions if there was a
> problem with transmission. In particular, the HTTP transport buries all
> exceptions, and it is impossible to tell on the client side if there was a
> problem with the transmission (such as the remote server not being available).
> WS-I BP 1.1 specifies the following:
> "The HTTP response to a one-way operation indicates the success or failure of
> the transmission of the message. Based on the semantics of the different
> response status codes supported by the HTTP protocol, the Profile specifies
> that "200" and "202" are the preferred status codes that the sender should
> expect, signifying that the one-way message was received." [2]
> And that
> "HTTP uses the 5xx series of status codes to indicate failure due to a server
> error." [3]
> I hope this is enough information....
> [1] http://marc.theaimsgroup.com/?l=axis-user&m=113499264305272&w=2
> [2]
> http://www.ws-i.org/Profiles/BasicProfile-1.1-2004-08-24.html#One-Way_Operations
> [3]
> http://www.ws-i.org/Profiles/BasicProfile-1.1-2004-08-24.html#HTTP_Server_Error_Status_Codes
--
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
