On Tue, Oct 14, 2008 at 6:00 PM, Gili Tzabari <[EMAIL PROTECTED]>wrote:
> 1) Why would you want to identify these classes in the first place? I > mean, who cares whether the class is created by Guice or by someone else? Tools, anyone who's reading the code and cares to debug where the arguments are coming from. > 2) Is this ability worth the cost of explicit annotations? Is it worth > losing the ability to inject/integrate with 3rd-party libraries? Yes. Provider methods will make 3rd party integration easy enough. > 3) Doesn't @Inject just mean that it *can* be injected by Guice, not > that it necessarily is? Don't user Modules already give you most of this > information anyway? Yes, it means that it can be injected, and no, modules don't give you all the information. Consider JIT (formerly "implicit") bindings. > Sorry to beat a dead horse :) I'm also surprised that no one else in > the community has an opinion (either way) on this matter...? TMK, Jesse, Kevin, and I all agree. Bob --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
