Then again, abortWith() does make sense from a client perspective
though:ClientRequestFilter and ClientRequestContext. In the client
cache example, you certainly don't want an exception to propagate back
up to application code when you abort the request with a cached entity.
If you want symetry between client and server request filters, then
maybe abortWith() has to stay.
On 2/18/2013 10:26 AM, Bill Burke 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