> @Ales > The more I've worked on this and thought about it, the more I realize > I still don't understand something very basic that you said: > "You need to understand what you're actually getting with this > integration. > You only get a way to tell MC' kernel how to lookup / inject your > Guice bound instances based on class or key. " > I think I only need it to look up based on class, but then I don't > really know. My brain is getting too frustrated and fried from all > this to know anything anymore!
"based on class or key" only means we support simple type matching injection, aka autowiring. The key (actually should be Key) is only there b/c Guice Injector api supports this the same way it does for Class, and the fact that MC keys can be any Object instance, meaning it can be Key instance as well. -- 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.
