Starting to use guice on a project of ours.. the server I'd like to use guice on has a number of endpoints.. some servlets, some hand- built tcp server sockets... i understand the need to build Injectors at the endpoints to bootstrap the dependency injection... but I'm not sure what the best practice is for organizing modules.... I have the server broken up into a number of modules for compiling purposes, but it's unclear to me how i ought to set up the Guice Modules for each of these....
For instance. Imagine a communication module that runs some tcp server sockets, and a web service module that runs some servlets... both depend on a core-service module... Presumably, all three would have needs, and would potentially want to define their own Guice Modules... Is it common practice to have the Injectors defined at these endpoints know about all of their dependencies' Modules and cnofigure the Injector with them? That seems messy.. I'm assuming there's a pattern here that I'm missing. Thanks in advance, Phill --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "google-guice" 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?hl=en -~----------~----~----~----~------~----~------~--~---
