users@jax-rs-spec.java.net

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

From: Santiago Pericas-Geertsen <Santiago.PericasGeertsen_at_oracle.com>
Date: Wed, 12 Sep 2012 12:36:55 -0400

On Sep 12, 2012, at 11:37 AM, Bill Burke wrote:

>>>>>> IMO, no filters should be executed until the resource method is
>>>>>> matched except for PreMatch filters.
>>
>>
>> (also from the context) seems to suggest no response filters should be run if pre-matching request filter aborts the processing with a response.
>>
>
> You took me out of context. I was talking about post-match global request filters and that they should be sorted and executed with name-bound filters.
>
> Should global response filters be executed from a pre-match abort? I think so? Thoughts?

 Yes, I believe it's explained in the spec. The only caveat for users is things like @ResourceInfo which won't be available; methods in that class can return null according to Javadoc.

-- Santiago