Well, Spring is a broader tools than Struts.  Spring MVC is more like a
direct counterpart of Struts, as a web framework.  There are other parts in
Spring you might find useful.  For example, Spring JDBC template, AOP
transaction control,  or  IoC container to manager business logic.  In my
case, I also use their scheduler improvement to wire beans. It is a more
elegant solution to me compaing to write into the hard code.   (
http://static.springframework.org/spring/docs/2.5.x/reference/scheduling.html#scheduling-jdk-timer)
As I mentioned in previous email, I am using struts 1.2  to manage the web
request handling, while using spring more as a middle tier tools within the
business logic and actions.  As the other guy points out, Spring is kind of
like the full set of Apache Commons, you can use them in all, or just use
whatever you find useful.  And good thing for Spring is that it can be used
in either way, full framework or just a part.  Here is the way I am using.
http://static.springframework.org/spring/docs/2.5.x/reference/web-integration.html#web-integration-common


Also, in Spring's package, one of the pet-store examples is Struts
1.2+Spring.  You can refer it as well.

Sincerely
Zhu, Guojun


On Wed, Jan 28, 2009 at 5:32 PM, johnrock <johnpi...@yahoo.com> wrote:

>
> Much Obliged everyone! It can seem overwhelming at first and I guess I have
> been searching for the burgeoning best practices of Spring 2.5 in a basic
> web app to help me focus in on where I should think about implementing it
> first...I have used Struts2 and especially liked the validation framework
> for handling forms, but is it overkill to think about using Struts2 and
> Spring2.5?
> --
> View this message in context:
> http://www.nabble.com/Is-Spring-worth-it--tp21692769p21717674.html
> Sent from the Struts - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
> For additional commands, e-mail: user-h...@struts.apache.org
>
>

Reply via email to