P.S. By "rather poor designs features" of Struts 1, I refer primarily
to choice of making Actions singletons, which required a separate
ActionForm bean. As I've read the history of Struts 1, WebWork, and
Struts 2, much of it written by the members of this list, I see that
they've acknowledge the drawbacks of that approach and have learned
from it. By no means did I mean to disparage the Struts 1 team. The
nature of software is that it gets better with time as we refine our
designs.
That said, it's interesting that the Spring MVC team decided not to
learn from, and instead repeat, this mistake.
On Mar 13, 2008, at 12:33 PM, Jim Cushing wrote:
I'm but a humble Struts 2 user (and a Spring MVC critic), so forgive
me for lurking on this list (it's a great way for me to follow the
progress). I posted two comments to that blog (search for "jimothy")
that I think sum up Spring MVC vs. Struts 2 from a mindshare
perspective. I'd be interested to hear how those in the thick of
Struts 2 development feel about this.
On Mar 12, 2008, at 11:41 AM, James Mitchell wrote:
Interesting read...
http://www.oreillynet.com/onjava/blog/2008/03/spring_mvc_javafx_google_web_t.html
--
James Mitchell
---------------------------------------------------------------------
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]
