On 18/02/13 15:26, 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().
>
Keeping abortWith() allows for a 'cleaner' blocking of the request IMHO;
besides throwing the exception implies it needs to be mapped, so why
request users register mappers to get blocking of the requests supported
if a simpler option is available ?
Cheers, Sergey