Karthik, > Have you looked at multibinding?
That looks good, but a side-concern of mine is that whatever functionality I discover in this regard also be available in Guice's client-side cousin, GIN. For this reason, I was hoping to stick with major releases. Have you any thoughts on my design issue here: I'm attempting to follow the Guice DI design imperative and not use new(), but how to generate simple generic containers as return values? I gleaned from Dhanji's Google IO 2009 talk that DI can help one write better code by forcing one to think about depedencies. In this case, however, I can't see how to get any simpler with Guice 2.0 than attempt a return of some java.util generic container. Thanks, Grary -- 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.
