Would it be totally unjustified to say this is working around the problem not solving it. Consider I m using Components A and B to build up Component C. Except that component A and B are layered compnents build using 50 other components.
Now what this would mean is in Component C if I need a Logger I can no longer setup a binding inside a module since chances are its used by one of the lower components with a different binding so I only ever have to use Providers. Perhaps I am missing something colossal in which feel free to point that out and I ll go back and reread Guice docs /watch the videos (which are excellent btw) and play with the examples/tests in the source package :) banks On Feb 28, 2:24 pm, Bob Lee <[email protected]> wrote: > On Sat, Feb 28, 2009 at 2:12 PM, bank kus <[email protected]> wrote: > > Though we still need to solve this problem where a top level component > > requires an extremely low level component while some of the components > > it uses also use this low level component with different bindings. > > You can also use provider methods (for example to construct the fireplace > manually and make sure you throw in the right piece of wood). > > Bob --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
