Give guice 3.0 and FactoryModuleBuilder a shot. It's a rewritten and better way of dealing with assisted inject.
sam On Mar 30, 2011 8:30 AM, "cowwoc" <[email protected]> wrote: > It looks like guice-assistedinject attempts to resolve the UriInfo > binding when FactoryProvider.newFactory() is invoked, but Jersey only > defines the UriInfo binding at a later part of the Module. > > I was under the impression that guice bindings are only supposed to > get resolved at Injector-creation time. Is there a way to defer > AssistedInject's type resolution to that time? > > Thanks, > Gili > > > On Mar 29, 3:44 pm, cowwoc <[email protected]> wrote: >> Hi, >> >> Using Guice 2.0 I am able to @Inject top-level Jersey components whose >> constructor refer to UriInfo, however when I try using AssistedInject >> for constructors referring to UriInfo I get this error: >> >> No implementation for javax.ws.rs.core.UriInfo was bound. >> >> JerseyServletModule defines the following bindings: >> >> @Provides >> @RequestScoped >> public UriInfo uriInfo(WebApplication wa) { >> return wa.getThreadLocalHttpContext().getUriInfo(); >> } >> >> @Provides >> public WebApplication webApp(GuiceContainer guiceContainer) { >> return guiceContainer.getWebApplication(); >> } >> >> Why would the two injection types differ? Any ideas? >> >> Thanks, >> Gili > > -- > You received this message because you are subscribed to the Google Groups "google-guice" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to [email protected]. > For more options, visit this group at http://groups.google.com/group/google-guice?hl=en. > -- You received this message because you are subscribed to the Google Groups "google-guice" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-guice?hl=en.
