On 30/01/13 19:10, Santiago Pericas-Geertsen wrote:
>
> On Jan 30, 2013, at 10:29 AM, Bill Burke<bburke_at_redhat.com> wrote:
>
>> The section on filters and exception handling is unclear.
>>
>> if an exception is thrown from a resource method:
>>
>> 1. An exception mapper is found
>> 2. bound and global filters are executed on the response
>>
Yes - this is my understanding too
>> If an exception is thrown from a request filter:
>>
>> 1. An exception mapper is found and executed
>> 2. response filters are executed. BOund response filters only executed if this is not prematch
>>
Why global response filters would not be executed but bounds one will in
this case ?
>> If an exception is thrown from a response filter:
>>
>> 1. An exception maper is found and executed
>> 2. ??? I assume no response filters are then executed?
I guess given that global response filters are executed after bound
response filters, should they be given a chance to process a response
too, right ?
>
> We had some discussions about this, but I don't remember exactly when (I could try to dig them up). The idea was to try to simplify things without having special cases for exceptions thrown here or there. Thus, Section 6.7 states that the response filter chain is always executed, regardless of where the exception was thrown, but exceptions are mapped only once.
>
Sergey
> -- Santiago
>