Ah, sorry :-)
So the ResourceContext is still the way to go then?
Give me a nod if there is anything I can try out to help!
Many thanks
Ian
-----Original Message-----
From: Paul.Sandoz_at_Sun.COM [mailto:Paul.Sandoz_at_Sun.COM]
Sent: 13 November 2009 15:36
To: users_at_jersey.dev.java.net
Subject: Re: [Jersey] JCDI dependency injection with Jersey
Hi Ian,
I can reproduce this. It is a *nasty* bug :-(
The problem is the injection information is initialized too early
before all the injection-related providers are registered.
Paul.
On Nov 13, 2009, at 4:03 PM, Ian Carr wrote:
> Hi, I have been doing some investigation of the JCDI injection
> mechanism and Jersey.
> I have been using the later builds of glassfish v3 (builds 71 & 72)
> with some success.
> However a change in the behaviour in build 72 has prompted me to the
> following question.
>
> (I do realize that all of this is still experimental, but am
> interested in where it's headed)
>
> Will I be able to mix and match the injection techniques @Inject and
> @Context or will one supercede the other?
>
> my sample code:
>
> @Path("/")
> @ImplicitProduces("text/html;qs=5")
> @XmlRootElement
>
> @ManagedBean
>
> public class MainResource implements Serializable {
> private static final long serialVersionUID = 1L;
> private static final Logger __log =
> Logger.getLogger(MainResource.class.getName());
>
> @Inject
> private BeanManager _manager; <<< the JCDI injection manager
>
> @Inject
> ConnectionManager _connManager; <<< my producer object
>
> @Context
> ResourceContext _rctxt; <<< The jersey resource context
>
> @Context
> HttpContext hctxt; <<< The jersey Http context
>
> In glassfish v3 build 71 which used jersey version 1.1.3-ea, all 4
> objects are injected when the ManagedBean annotation was present,
> but (correctly!) only the two jersey objects without the managedBean
> annotation.
>
> But having installed build 72 (which appears to incorporate the
> 1.1.4 release of jersey) this morning and tried the same application.
> the @Inject parameters and the HttpContext are injected if the
> ManagedBean annotation is present but the ResourceContext is not.
> If I remove the annotation the HttpContext and ResourceContext
> (instance of
> com.sun.jersey.server.impl.application.WebApplicationImpl$6) are
> injected.
>
> I was assuming that even when using the ManagedBean resources I
> would still inject the jersey ResourceContext object to create sub
> resources as per the spring examples, and would therefore take
> advantage of Jersey deciding where injected objects came from.
> Or is the intention that I would use the JCDI bean manager to derive
> the sub resources? but presumably that precludes a mixed object
> source solution?
>
> again appologies if this is too early to be trying this stuff!
>
> Thanks for a great framework
>
> Ian
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_jersey.dev.java.net
> For additional commands, e-mail: users-help_at_jersey.dev.java.net
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_jersey.dev.java.net
For additional commands, e-mail: users-help_at_jersey.dev.java.net