jsr339-experts@jax-rs-spec.java.net

[jsr339-experts] Re: [jax-rs-spec users] Re: ContainerResponseFilters must not be executed on subresource locator methods

From: Marek Potociar <marek.potociar_at_oracle.com>
Date: Mon, 10 Sep 2012 18:23:18 +0200

Fixed,

Marek

On Sep 10, 2012, at 4:39 PM, Bill Burke <bburke_at_redhat.com> wrote:

> IMO, no filters should be executed until the resource method is matched except for PreMatch filters.
>
> On 9/10/2012 10:09 AM, Sergey Beryozkin wrote:
>> 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
>
> --
> Bill Burke
> JBoss, a division of Red Hat
> http://bill.burkecentral.com