Issue 253: new feature - search packages for objects to instantiate http://code.google.com/p/google-guice/issues/detail?id=253
Comment #1 by robbie.vanbrabant: To clarify what you probably meant, I put up a small comparison a while ago: http://code.google.com/p/garbagecollected/wiki/GuicySpring You can pretty much already do that with @ImplementedBy, @ProvidedBy and scope annotations, without classpath scanning. What you can't do in 1.0 using these mechanisms: - binding annotations - scope annotations on the interface that has @ProvidedBy, @ImplementedBy (only on the impl), I think this has been fixed in 2.0. - failing early (these are JIT bindings, with classpath scanning you'd generate explicit bindings, I suppose) I think Spring 2.5's self-annotated beans are plain ugly, and that we shouldn't have had @ProvidedBy and @ImplementedBy in the first place. Guice should stay away from it as far as possible. So as you mentioned, this could be an extension to Guice which you could offer as a separate download. And maybe we should even remove @ImplementedBy, @ProvidedBy from a future Guice version... -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "google-guice-dev" 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-dev?hl=en -~----------~----~----~----~------~----~------~--~---
