Re: [jaxrs-dev] New Exception Handling Use-Case

["Markus KARG" <markus@xxxxxxxxxxxxxxx>]

So your proposal would be that the spec shall define a generic exception that all implementations MUST throw instead?

-Markus

 

 

From: jaxrs-dev-bounces@xxxxxxxxxxx [mailto:jaxrs-dev-bounces@xxxxxxxxxxx] On Behalf Of Rebecca Searls
Sent: Montag, 22. Oktober 2018 18:46
To: jaxrs-dev@xxxxxxxxxxx
Subject: [jaxrs-dev] New Exception Handling Use-Case

 

There is a use-case where the user wants the opportunity to return a Response
object for an exception the jax-rs container does not handle (see spec section
3.3.4 Exceptions).  List item 4 in section 3.3.4 states, "Checked exceptions
and throwables that have not been mapped and cannot be thrown directly MUST be
wrapped in a container-specific exception ..."  This is not helpful to the user
because such exceptions are container implementation specific.  It does not
define a standard class(s) for which a user can provide a ExceptionMapper provider
to evaluation unhandled exceptions.

It is asked that additions be made to the spec to handle this scenario.