Hi
The documentation for ContainerResponseFilter suggests that say
name-bound response filters can be executed after a subresource locator
method has been invoked.
However, the actual response is not even available at that stage, we are
still in the process of locating the actual resource method - it is only
available after a final resource method has been invoked.
I'd like to suggest that the documentation is clarified in that regard.
Also, ContainerRequestContext docs probably need to be updated to say
that IllegalStateException is to be thrown whenever one of its 'setter'
methods is invoked as part of the response filter chain execution
Thanks, Sergey