Guice needs to know about the types that are bound, that is true. If you're looking to, say, *combine* interfaces - i.e. dynamically implement Foo & Bar - that's not going to work without a concrete type that combines Foo and Bar.
But just-in-time binding is a solution, not a problem. What problem are you trying to solve? -Tim -- You received this message because you are subscribed to the Google Groups "google-guice" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-guice. To view this discussion on the web visit https://groups.google.com/d/msgid/google-guice/6358980b-6b17-4a8f-87b1-36ef3b982866%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
