I have started using jersey with the jersey-spring integration, and had a
pretty basic ExceptionMapper provider working with the 1.0 release.
However, when I switch to the 1.0.1 or 1.0.3 release, my exception mapper
is no longer detected.
I'm not doing anything special - my class is annotated with @Provider and
implements ExceptionMapper<Throwable>. I chose throwable because I simply
wanted a single mapper that would generate a valid response for any
exception that may occur.
Has something changed with the provider scanning? Is there a change I need
to make in my code for this to work?
Thanks,
David Johnson