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.
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? 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
