Forgot to mention bind(S2.class).to(S2I.class); // the S2I "JIT" ends up at parent bind(S3I.class); // the S3I "JIT" ends up at child as expected
Cheers, Alen On May 17, 1:01 am, Alen Vrecko <[email protected]> wrote: > I've debugged a little bit. It is cool to see the inner workings of > Guice. It looks like: > > The createChildInjector's injector JIT bindings end up at the root > injector (which is already fully "initialized" and is not > "reinitialized") therefore the bindings just sit there and don't get > processed. Probably better if they'd wind up at the child injector > like it happens with PrivateModules or something. > > Probably the easiest if just use explicit bindings instead of > @Singleton. > > Cheers, > Alen > > On May 16, 8:36 pm, Sam Berlin <[email protected]> wrote: > > > Did you mean to reply with this in the other thread (about @nullable)? > > > Any insight into this child injector eager singleton issue? The > > @nullable one can be worked around, but I don't see a good way to > > workaround this. > > > Sam > > > On May 16, 2009, at 1:00 PM, "[email protected]" <[email protected]> > > wrote: > > > > Hey Sam, yeah sorry about this. It comes as a consequence of using > > > regular Guice stuff to create instances. I've added a note to the > > > docs. > > > http://tinyurl.com/pn4uca > > > > If there's any other doc that could be improved, please let me know! > > > Or submit patches! --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
