Thanks Sergey!
I have almost put it together at this point.
One thing that wasn't immediately clear is that the exception mapper is a
provider
and can be registered as follows (makes sense to add to the same wiki
page?):
jaxrs:providers
ref
In the end I wipped up something like this, which seem to be serving the
purpose.
Now I need to figure out how to do something similar on the Soap side.
public class RestExceptionMapper implements ExceptionMapperException
{
private static Log logger =
Registering a custom out fault interceptor might do the trick and you
can handle both JAXWS and JAXRS exceptions from there...For ex, if the
in message has an application/soap content type then WSBaseException has
to be handled one way, otherwise it is a JAXRS service exception
Cheers, Sergey
From my understanding you basically want a centralised place to handle
exceptions and a way to control what is returned to the client? We use an
exception mapper which receives all possible exceptions and you can then
return the desired response object based on the exception. We have a many
to one
Hi Mustafa!
Yes, I need to be able to have a centrally controller backstop for all
exceptions coming out of my mackages, mostly .*Impl classes and custom
interceptors such as i.e. Auth interceptor. Soap already kind of does it for
me by wrapping it into a generic Fault (I actually wanted
