The webservice responds with a stacktrace instead of a soap fault if malformed xml is sent.
Unable to handle Exception when endpoint invoked with invalid XML
We currently have SOAP services in production that still provide a stack-trace when malformed XML is sent to them - this is a very difficult bug to deal with and there is currently no work-around
This ruined a better part of my day. The endpoint resolvers are pretty useless. This really needs to be fixed. I had to extend the servlet to get around this, feels totally hacky, but can't sort out any other way.
John, not sure if it's too late to help, but you could create a servlet filter and wrap the chain.doFilter() method in a try-catch block for NestedServletException. You can look at the cause to see if it's an invalid XML related issue, and take action that way. It's slightly better than having to extend the MessageDispatcherServlet, but really not by much. It would be nice to see this issue resolved.
What I have done is to define a custom MessageReceiverHandlerAdapter that is used by the default spring-ws MessageDispatcherServlet. That works and I think is the way to handle this by design. I can provide the code if needed.
As of version, Spring-WS throws a InvalidXmlException when dealing with invalid XML. By default, this exception results in a 400 status code, but it can be changed by overriding WebServiceMessageReceiverHandlerAdapter.handleInvalidXmlException,