Thats not really what I want, since the all the instances that I am after already exists in the parent module, so I can't get around this without creating a binding that is specific to the child module, and injecting that to every child component. The counterintuitive thing here is the fact that something that was bound in a child injector, that has type listeners associated with it, won't be get those type listeners applied... .
On Aug 5, 3:37 pm, "[email protected]" <[email protected]> wrote: > On Aug 5, 3:28 am, kimchy <[email protected]> wrote: > > > So basically this means that I need to have each bindable element in > > the child module be injected with something that is defined only > > within the child module? Even if it does not really requires it? Is > > that what you mean in explicit binding in the child module? > > Types can be injected with dependencies from either the same injector, > or an ancestor (parent) injector. Just-in-time bindings will always be > created in the top-level injector that satisfies all of their non- > optional dependencies. If you want a binding to live in a specific > child injector, you can do so by making that binding explicit in that > injector's module. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
