[ https://issues.apache.org/activemq/browse/SM-477?page=all ]
Renaud Bruyeron updated SM-477: ------------------------------- Attachment: patch.txt this patch fixes the issue above: when the exchange is Done (i.e. in-only or robust-in-only) we send a HTTP 202 instead of the default HTTP 200. > servicemix-http does not reply with HTTP 202 when processing "oneway" SOAP > messages > ----------------------------------------------------------------------------------- > > Key: SM-477 > URL: https://issues.apache.org/activemq/browse/SM-477 > Project: ServiceMix > Type: Bug > Components: servicemix-http > Versions: 3.0-M2 > Environment: 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? > Reporter: Renaud Bruyeron > Fix For: 3.0 > Attachments: patch.txt > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira