[jax-rs-spec users] [jsr339-experts] Re: Re: Re: FilterAction and FilterContext

From: Sergey Beryozkin <>
Date: Thu, 1 Dec 2011 15:50:05 +0000

Sorry about the previous response, it got somehow messed up, please see
the response below
>> IMHO, FilterContext.setResponse(...) is a very cryptic way of saying
>> that the request filter chain execution is stopped
>> and the response processing should be resumed. It's certainly not
>> immediately clear that this operation breaks the
>> filter chain.

The response:

> What is so cryptic about it ?
> I'm a filter developer and I know that my filter may be able to provide
> a Response or update the current request properties. If the Response is
> available then I set and I'm done; As a filter developer I'm not
> thinking about chains which needs to be stopped or resumed elsewhere, I
> just think that this is a Response, let the runtime worry about making
> it available to the consumer. Is it really cryptic ?
> IMHO it certainly less than also returning NextAction alonside setting
> the Response on the filter chain - and getting this state of mind that
> my filter needs to tell the runtime what it should do next.
> Sergey
>> Marek
>>> Cheers, Sergey
>>>> BTW, We're starting to implement the spec next week. I'll probably have
>>>> a lot more comments when we start playing with things.

Sergey Beryozkin
Talend Community Coders