Hmm - that sounds weird...
I would expect that a class annotated as a no-interface EJB would always be treated as such - I would never have expected it to be treated as a POJO in any context, as long as it's being deployed to an EJB3 container...
Moises
On Apr 26, 2010, at 9:47 AM, ljnelson wrote:
> On Mon, Apr 26, 2010 at 10:39 AM, Paul Sandoz [via Jersey]
> <[hidden email]> wrote:
> > Jersey will look up the EJB using the class name to derive the
> > portable JNDI name, and i think the reference obtained from JNDI does
> > not implement ContextResolver. Need to verify.
>
> And to be clear, I don't need the implementation of ContextResolver to
> be accessed through a bean reference. I would expect that the bean
> instance would simply be created like any other POJO for these
> purposes.
>
> L
>
> View this message in context: Re: ClassCastException on deploying ContextResolver?
> Sent from the Jersey mailing list archive at Nabble.com.