I use individual components of Spring for targeted tasks: JMS, JDBC legacy interfaces, etc. The XML I keep as lean as possible (the less XML the more I enjoy my job). The Spring context is manually initialized as I use Guice Filter as my entry point in the Web container. The various Test harnesses, obviously, also manually initialize the two DI contexts.
The equivalent of features 1-3 mentioned below are indeed provided by Spring, though the semantics differ. (import versus install for instance). On Tue, Mar 1, 2011 at 8:05 PM, zixzigma <[email protected]> wrote: > could you please explain for what purpose you use each of Guice and Spring > in your development ? > how you separate the responsibility ? > > the following features in Guice I would like to use, which I don't think > are available in Spring, I can be wrong. > 1- Providers (is Spring FactoryBean serving similar purpose ?) > 2-Assisted Inject > 3- Modular approach, having GinModules, and adding them to injector. (is > Spring @Bean Java Configuration similar to GinModules?) > > > Thank You > > -- > 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. > -- 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.
