I'm curious, I like the fact that you can use annotations, but if you annotate your interfaces with @ImplementedBy aren't you breaking the whole concept of DI? I would think the point of using a DI framework is that if I wanted I could quickly swap out the implementations (in guice, using a different module, in spring different config file.)
Maybe a better approach for rapid development is to start out actually coding just your implementations with the name MyClass (as opposed to something like MyClassImpl). Later when you forsee the nee of providing a different implementation (like possibly for tests) then just push your code into an implemenatition class name and make MyClass an interface. The refactor would be easy. Does anyone else take this approach? -- Rick --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
