Thanks Stuart and Sam, yep. I guess it is the JIT binding. So if I use concrete classes, with the @Inject, I may not need to add them to the module.
Thanks On Feb 6, 5:08 pm, Stuart McCulloch <[email protected]> wrote: > On 6 Feb 2012, at 05:21, egolan wrote: > > > Hi all, > > I have created the modules, and very happy with the results. > > I even created several (not too much) modules, based on the logic > > modules of the app. > > > I did some experiments and remarked bindings that were Untargetted > > Bindings... > > And magically everything worked :) > > > So my guess is, and I probably missed reading it somewhere, that Guice > > can do automatic binding based on the annotations and dependencies. > > And that it searches the class path. > > > Am I correct? > > As Sam said Guice core doesn't do classpath scanning - though there are > extensions to add this ( previously discussed > onhttp://groups.google.com/group/google-guice/browse_thread/thread/6818...) > > You might be seeing the Just-in-time binding > support:http://code.google.com/p/google-guice/wiki/JustInTimeBindingswhere if > Guice sees you need a concrete class then it adds an untargetted binding for > that class. > > > > > > > > > Thanks, > > > Eyal -- 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.
