2009/3/2 Bob Lee <[email protected]>: > On Mon, Mar 2, 2009 at 1:04 AM, Witold Szczerba <[email protected]> > wrote: >> >> Imagine I am writing application using Guice. Everything works fine, >> but one day I decide to use some 3rd party library. This library uses >> Guice to wire itself and exposes only public stuff. Now I am creating >> new, empty project to see if that library works as I am expecting and >> everything is fine until I use it in my real project. What happens? >> That 3rd party lib uses __internally__ some binding which happens to >> be one of my global binding. Why, on Earth, some internal stuff of >> that library goes into collision with my project's stuff? > > If you want to wire up the internals of your library, I'd use a separate > Injector so there's no interference. > > Bob
I think that is the way to go! Every separate/3rd vendor library can use its own injector and I could use that injectror in my module which would wire that lib with my project (with my application's main injector). That approach seems to be much more flexible as 3rd vendor libraries can use different version of Guice or different IoC like PicoContainer or Spring... Witold Szczerba --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
