On 9/12/2012 6:37 AM, Marek Potociar wrote:
>
> On Sep 12, 2012, at 12:12 PM, Sergey Beryozkin <sberyozkin_at_talend.com> wrote:
>
>> On 12/09/12 10:55, Marek Potociar wrote:
>>> All right,
>>>
>>> One more iteration on the subject: *We MUST support response filters
>>> that are executed even if a resource has been matched. *
>>>
>> Not sure why you are highlighting, thought it was obvious
>
> Well, since @PreMatching was dropped for the response filters (based on your suggestion), the Bill's sentence:
>
>>>>> 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?
Bill
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com