Comment by phasmal: *limpbizkit:* Sorry, I was meaning to ask a question about the design choice, not the code used.
To rephrase: If the BillingService constructor code was changed to accept a BillingModule instance then this (the code in my second example above) seems to me to be a simpler way of injecting these dependencies (inside the BillingModule instance, perhaps implemented like a read-only bean) while still managing an arbitrarily complex graph of dependencies (again, implemented inside the BillingModule class). For more information: http://code.google.com/p/google-guice/wiki/Motivation --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "google-guice-dev" 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-dev?hl=en -~----------~----~----~----~------~----~------~--~---
