users@jersey.java.net

[Jersey] Spring managed bean as a Provider

From: naresh <baliga_naresh_at_yahoo.com>
Date: Tue, 16 Jun 2015 14:36:57 -0700 (MST)

Hello,

I'm using Jersey 2.5.1, Spring 4.0.3 for IoC and Jackson 1.9.11.

I've discovered that if I try to provide a custom ObjectMapper through the
following ContextResolver:


@Component
@Provider
public class JacksonObjectMapperContextResolver
      implements ContextResolver<ObjectMapper>
{....}


Jersey seems to be unable to find the provider.

However if I make it a non-Spring managed bean by removing the @Component,
Jersey can find the ContextResolver just fine and therefore my custom
configured ObjectMapper comes into play.

I believe this used to work in Jersey 1.5.

Any help is appreciated.




--
View this message in context: http://jersey.576304.n2.nabble.com/Spring-managed-bean-as-a-Provider-tp7583347.html
Sent from the Jersey mailing list archive at Nabble.com.