Comment by [email protected]:

Hi, this looks like a cool way of doing IoC. Where is the best place to put the Injector in a web app, like Spring MVC on Apache? And now we have a global Injector object that we always use instead of using the new operator? What's the best way to give access to the Injector throughout the app?

What have people found about how best to structure your configuration modules? I'm thinking all those bindings would get really big in a large app and would be a source of svn workflow conflicts.

For more information:
http://code.google.com/p/google-guice/wiki/GettingStarted

--
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.

Reply via email to