Rebecca,
I understand the issue with using container-specific exception types, that is clearly a very old statement about JAX-WS and Servlets. However, the statement includes the pre-condition “that have not been mapped”.
So why not map them using some base exception type? Mappers are selected based on type distance, so it should not affect other, more specific mappers. Perhaps I’m missing something about the use case.
— Santiago
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.
_______________________________________________
jaxrs-dev mailing list
jaxrs-dev@xxxxxxxxxxxTo change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jaxrs-dev
