On Jan 26, 2:28 am, Clinton Begin <[email protected]> wrote: > Let your community speak for itself, as I'm sure it will. ;-)
Makes sense. Would you still please say on this mailing list, that what were the design decisions that lead to the requirement of @Inject? There are quite many frameworks which have gone the other way, that they inject constructors without any annotations. What are the pros and cons of either approach? It would even be useful to have the motivation for requiring @Inject to read in the web site's FAQ. -- 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.
