users@jersey.java.net

Once a Resource, never a Provider?

From: Laird Nelson <ljnelson_at_gmail.com>
Date: Mon, 26 Apr 2010 20:22:45 -0400

I am still doggedly on the trail of getting JAXB to do what I want.

After some earlier messages on this list, I moved my
ContextResolver<Class> implementation out of an EJB bean class and
into an existing resource class. I don't want to create more classes
unless I have to.

It looks like I have to. My resource class is discovered at
deployment time as a resource, but not as a ContextResolver<Class>
(even though it's annotated with the @Provider annotation.

Is it true that if you have a resource class, then that resource class
cannot also be a context provider? Or is there yet another mystery in
JAX-RS dependency injection going on?

Thanks,
Laird