While the users of the EDSL are aware of Guice, the requirement for
callers to extend a particular abstract class
is too strong, not to mention incompatible with previous versions of the
EDSL. This is not a requirement that Guice EDSLs typically impose, and a
module would not be able to use two such EDSLs because one cannot extend
two abstract classes.
So I seem to need some way to do one of:
* Change the injection key for a binding
* Defer configuration of an installed module at least until the
enclosing module returns from its configure method
* Remove a binding made earlier in the module
--
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 https://groups.google.com/group/google-guice.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-guice/56FC69A0.50709%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
