users@jersey.java.net

Re: [Jersey] ExceptionMapper provider not detected

From: Paul Sandoz <Paul.Sandoz_at_Sun.COM>
Date: Fri, 22 May 2009 08:45:16 +0200

On May 22, 2009, at 4:10 AM, davidj_at_lynxlogic.com wrote:

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

Only if your component is a registered as a Spring component (as you
did below).

Non-Spring-based Providers are registered in the same way as root
resource classes (e.g. declare packages).

Did your registration mechanism in the web.xml change when you
switched from Jersey 1.0 ?


> whereas in 1.0 just having @Provider
> was sufficient. I annotated my ExceptionMapper with Springs
> @Component and
> it worked fine.
>

Great.

Paul.