While S2 uses an internal DI container (an early forked version of Guice), it shouldn't be used by end user applications, and therefore, Spring is generally the preferred DI container for S2 applications. The popular Struts 2 Spring plugin provides this integration support.
Interestingly, there are also Struts 2 plugins for Spring MVC and Spring WebFlow integration support, although they aren't anywhere near as widely used. http://cwiki.apache.org/S2PLUGINS/home.html Don On 3/16/07, Rick Schumeyer <[EMAIL PROTECTED]> wrote:
Dave Newton wrote: > --- Rick Schumeyer wrote: > >> I had thought that Spring was another framework, >> and that you would use either S2 or Spring but not >> both. >> > > Spring provides a lot of different functionality; > Spring MVC is the web-ish portion of it. You probably > (but you can!) would not use both Spring MVC and S2. > > >> Could someone explain why you would use S2+Spring? >> > > Dependency Injection (DI, IoC) is the big win for me, > but other parts of Spring may be useful (AOP, > Db-related things, and Acegi... uh.. spring to mind). > > >> I'm assuming that if I use S2, Spring is optional? >> > > Yes... but the DI bits are *very* useful, and trivial > to learn. > > d. > But doesn't webwork/S2 also provide DI/IOC? Or does Spring do this for the model part of MVC as well? (Sorry, still somewhat confused) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
