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

From: Santiago Pericas-Geertsen <>
Date: Fri, 2 Dec 2011 10:55:38 -0500


 Seems to me that all the options are on table now, and it's probably time to pick one and move forward. I can set up a poll, but based on what I read, I can almost predict the winner based on the 4 experts that were part of this discussion.

 The compromising solution seems be: (i) drop FilterAction and use void (ii) use setResponse() or a renamed version of it to signal termination. This is a very small change and, I think, what was originally proposed by Sergey.

 Can we all compromise and go with this or shall I setup up a poll to resolve this?

-- Santiago

On Dec 2, 2011, at 9:46 AM, Bill Burke wrote:

> On 12/2/11 7:25 AM, Marek Potociar wrote:
>> I cannot stop wondering how a single interface can cause such strong feelings. :)
> I'll be blunt here...Because, for me at least, this is just another small example of over-designing. The whole client interface is littered with the same kind mistakes and it just becomes aggravating and frustrating the more times you see it and the more times you have to argue over something simple.
> Just on Tuesday I had a meeting with a junior developer that works for me. He was trying to understand 2.0 by looking at the javadocs and was having a hard time. When I told him to check out the examples, it was a lot easier for him, but still, just looking at the API was a barrier for him.
> Anyways, thats my rant for the week. Enjoy....
> --
> Bill Burke
> JBoss, a division of Red Hat