I have a SOAP service, the request and responses work as expected with good input, if I specify bad input for an XML element
in request body:
...
<
I remember running into this kind of problem when working with spring-security. I also had issues with my exception resolver not being invoked under some condititions.
The problem then was that there is a filter chain that handles each request. The code that invokes the exception resolvers is a filter in this chain, but it is close to the end of the chain. Hence, if an exception ocurred somewhere within the filters before the exception resolver invoking filter, my resolver would never be invoked.
I am guessing you suffer from something similar here, where envelope parse errors happen before the exception resolver invoking filter. If that is the case, you will have to resort to some other way of handling those exceptions, for example a vanilla servlet filter.