That's the crux of my problem: I've got my own pluggable extension framework built on top of Guice and the semantics don't quite match closely enough: I want to use strings to match up extensions with their clients and it doesn't quite fit Guice's view of the world (but it's closely enough that it *should* work! ;) )
Anyway, I have restructured my use of Guice to get it close enough to what I want. Unfortunately, there's still a bit of boilerplate that I can't quite get rid of (I'm requirement extension writers to boilerplate a particular provider subclass) but it's not too bad. Thanks to all for information! -- You received this message because you are subscribed to the Google Groups "google-guice" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-guice/-/ccxrWZlzQWkJ. 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.
