Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
3.0-M2
-
None
-
See http://www.nabble.com/support-for-oneway-MEP-in-servicemix-http---tf1871975.html
When using Axis 1.4 to post a oneway SOAP message, servicemix-http replies with a HTTP 200, which the client interprets as a response. It should reply with 202 which is the right reply for async oneway processing.
I am not sure on the fix though: on what criteria should sm-http decide what http code to return? is it on the MEP declared on the endpoint, or on the wsdl, or both?
See http://www.nabble.com/support-for-oneway-MEP-in-servicemix-http---tf1871975.html When using Axis 1.4 to post a oneway SOAP message, servicemix-http replies with a HTTP 200, which the client interprets as a response. It should reply with 202 which is the right reply for async oneway processing. I am not sure on the fix though: on what criteria should sm-http decide what http code to return? is it on the MEP declared on the endpoint, or on the wsdl, or both?