I think the mention of "inheritance" at the top of this thread sent it off in some weird directions. You don't have an inheritance problem. You have a "one module binding orthagonal things" problem.
Split the stuff that will not be "overridden" out of your "parent module". Create a new module - we'll call it "common" that binds that stuff. For the remainder, have two modules, and only use one of them at runtime. One will be your stock bindings, and the other will be your "customized" bindings. It's really rare to need inheritance in writing Guice modules (or most anything, really); thinking in terms of inheritance can blind one to really simple composition-based ways of solving problems. -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. For more options, visit https://groups.google.com/groups/opt_out.
