On Wed, Mar 26, 2008 at 1:15 AM, Martin Webb <[EMAIL PROTECTED]> wrote:
> Very happy to go down the DI path. I have no experience in Guice, but > plenty in Spring. We (BT.com) will require consumption of existing > components built with Spring - so as long as we can inject Spring based > components within Guice based components failry easily then I have no > complaints about using Guice. Guice has a spring integration module just for this sort of thing. You can see it here: http://code.google.com/p/google-guice/source/browse/trunk/spring/ Of course, you may not need to do anything at all, depending on how you deploy Shindig. If you're using it as a back end blackbox server (ala mysql), you probably don't need to think about it much anyway. > > I'm not sure how we would swap out a Guice based component with a Spring > based component without wrappering the Spring based one within the Guice > based one? > > We also use Spring for JDNI datasouces, Hiberate and iBatis integration, > xn > semantics - does Guice provide any of this? No -- Guice focuses on IoC. Specific component integration is generally handled with provider wrappers. That said, you shouldn't need to change any of your existing spring stuff to use Shindig if we go with Guice. > > ps It may sound like it :) but I'm not religious about the use of Spring - > I > just need to know what we do/don't get with Guice, and then how easy it is > to use Spring on a needs-by-needs basis. > > Martin > > -- > Internet Related Technologies - http://www.irt.org > -- ~Kevin
