users@jersey.java.net

Re: [Jersey] ExceptionMapper provider not detected

From: <davidj_at_lynxlogic.com>
Date: Thu, 21 May 2009 20:10:59 -0600 (MDT)

Ok, I solved this myself. For anyone else who may run into this, it
appears in 1.0.1 the jersey-spring implementation changed to use only
Spring IoC for resolving providers, whereas in 1.0 just having @Provider
was sufficient. I annotated my ExceptionMapper with Springs @Component and
it worked fine.

> 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.