Whats the difference between @Provider methods in Modules and Providers interfaces. Basically what I understand that you call your custom provider whenever you need an object (provider.get()) and @Providers method is called whenever you need start a new Scope (Prototype for example). Can somebody explain the benefit of implementing a Provider? Basically I see a big drawback that by using providers guice dependencies get scattered all over your application code.
And the second question is about Springs <context:component-scan base- package="x.y.service">. Will guice have anything like this? As I know that it is possible to annotate an interface and specify the default Impl for it, but again, I don't want my API to have a dependency on guice. -- 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.
