SpringMVC: Create a second adapter only using a filter without the interceptor

[Sven Döring]

The current SpringMVC adapter uses a filter-interceptor combination to validate the request.

The filter is only used to wrap the servlet request that is used in the interceptor. The interceptor has advantages like default exception mapping. Without any more work the client receives proper error messages in JSON.

However the interceptor is not really necessary. The request validation could be done in the filter, too. But then the exception mapping is missing. A validation error would lead to a poor textual servlet response.

This can be changed. Just add a response writer to the filter in case of validation errors.

[Sven Döring]

As no one demands this feature it'll be only implemented if someone calls for it. Then a new ticket shall be opened.