You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
WebServiceMessageReceiverHandlerAdapter has been changed recently to catch InvalidXmlException and return a HTTP 400 status code. We would like to instead return a SOAP fault with a detailed message of the parse error (I'm not certain but returning 400 is probably against the SOAP spec). This is impossible with the new implementation of WebServiceMessageReceiverHandlerAdapter without re-implementing the handle(...) method.
Could the handling of this exception (and probably the non-POST transport method) be done by a separate protected method such that it can be overridden?
Damon Maria opened SWS-804 and commented
WebServiceMessageReceiverHandlerAdapter has been changed recently to catch InvalidXmlException and return a HTTP 400 status code. We would like to instead return a SOAP fault with a detailed message of the parse error (I'm not certain but returning 400 is probably against the SOAP spec). This is impossible with the new implementation of WebServiceMessageReceiverHandlerAdapter without re-implementing the handle(...) method.
Could the handling of this exception (and probably the non-POST transport method) be done by a separate protected method such that it can be overridden?
Affects: 2.1 GA
Referenced from: commits 4296756
The text was updated successfully, but these errors were encountered: