Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for SOAP v1.2 Fault to Status Code mapping in WebServiceTemplate [SWS-868] #942

Closed
gregturn opened this issue Mar 27, 2014 · 1 comment

Comments

@gregturn
Copy link
Member

@gregturn gregturn commented Mar 27, 2014

Phil McCarley opened SWS-868 and commented

SOAP v1.2 specifies that for SOAP Fault's with Code of "env:Sender" the HTTP response status code should be 400 (rather than 500 for all other faults).

http://www.w3.org/TR/2007/REC-soap12-part2-20070427/#tabresstatereccodes

This may need to be looked at on the server side (I haven't checked) but I am particularly interested only in the client side at the moment. I have a service that follows this advice and return the 400 code with the Fault content, however when using WebServiceTemplate with any WebServiceConnection based off AbstractHttpSenderConnection, the hasFault() method of that class will only return true if the code is 500.

Hence the problem that I am facing, which is that the response is simple considered an error and a simple WebServiceTransportException is thrown rather than the more useful SoapFaultClientException.


Affects: 2.1.4

Referenced from: commits ded1efd

@gregturn
Copy link
Member Author

@gregturn gregturn commented Apr 23, 2014

Arjen Poutsma commented

Fixed on both the client and server-side.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants