I'd support keeping abortWith(). I do not like style when exceptions are abused in non-exceptional code paths. And IMO from a filter perspective, aborting is not an exceptional code path. That's something very natural to filters.
Marek
On Feb 18, 2013, at 4:26 PM, Bill Burke <bburke_at_redhat.com> wrote:
> Since exceptions can be thrown from ContainerRequestFilter, do we need ContainerRequestContext.abortWith()? Instead the user can just throw an exception from the JAX-RS exception hierarchy to abort the request. Its pretty much the same thing, right, so I don't see an issue with removing abortWith().
>
> --
> Bill Burke
> JBoss, a division of Red Hat
> http://bill.burkecentral.com