So if I understand correctly, if I plan to use S2, I will also need to
swap out some part of S2 with some part of Spring (and deal with a
Spring learning curve)? And some people are using Spring MVC with S2?
But S2 is also an MVC framework? (And I haven't even asked about things
like tiles and hibernate yet!)
I don't hope to start a flame war, but I suspect it's stuff like this
that causes people to throw up their hands and use Ruby on Rails despite
its reputation for scalability problems. I suspect that experienced
java webapp developers may forget how overwhelming the java webapp world
can be, even for an experienced programmer (but not experienced in the
java webapp world).
In order to move forward, if I start developing something with S2, can I
add the Spring DI stuff later (without breaking my code) or do I need to
start off with Spring?
Out of curiosity, why shouldn't the S2 DI be used by end users?
And to push my luck with one more...if I need to be using parts of
Spring anyway...why not just use Spring? Why bother with S2? (Please
note this is an honest question...I'm assuming that S2 adds value to
Spring, but obviously I don't know what)
Don Brown wrote:
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
