Nicely done! On Jan 3, 2010 7:14 AM, "dg" <[email protected]> wrote:
With respect to "various various principles and practical concerns" -- I felt as you did, once. To paraphrase Churchill: It has been said that @Inject is the worst form of integration except all the others that have been tried. At first I found working with the annotations a little difficult, but then I started to respect them, my staff started to like them, and then you're home free. As a simple example, being able to open an interface, see @Singleton at the top and by that know the requirements of any implementation (with respect to thread safety, for example) is really a great thing. (You require that in javadoc anyway, right? Keeping that doc and @Singleton in the same file means they won't drift.) Putting the information close to your users means you don't have to keep saying "did you check the module" when somebody has a question. Annotations also scale well, since they reduce programmer-contention on the module file(s). So by all means, you can do everything you need to do in the modules, but I encourage you to at least give the @alternative a try. You might like it. -d On Dec 31 2009, 4:47 pm, JN <[email protected]> wrote: > I'm looking seriously into the possibi... -- 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.
