Webworks Vs Struts

[dinesh pande]

Hi,
Could someone please help me in taking a decision between using WebWorks and Struts as the WebApp Framework for our J2EE Applications.
If these have already been compared elsewhere, those links would also help.
Thanks

[Chris Mathews]

Moving to the Struts and Other Frameworks forum...

[Gregg Bolinger]

Possibly a bit biased since it is from the WebWork site but....
http://wiki.opensymphony.com/space/Struts+vs.+WebWork

[Jason Menard]

Originally posted by Gregg Bolinger:
Possibly a bit biased since it is from the WebWork site but....

Possibly? That seems to be a horribly biased piece imho. For one, the author admits in several places that he doesn't know much about certain parts of Struts, and at one point asks leading questions about part of the framework that he doesn't understand apparently attempting to influence the reader to draw a conclusion.
I don't know a thing about WebWorks, however from reading that comparison what I get out of it is that Struts uses standard J2EE mechanisms (Servlets, JSTL-EL, etc...) and WebWorks often does not. That's fine, but to try to spin it that these mechanisms are somehow bad seems a bit odd.
Overall, it looks like just a piece of marketing attempting to convince people to use their product instead of the de facto standard.

[Chris Mathews]

Originally posted by Jason Menard:
I don't know a thing about WebWorks, however from reading that comparison what I get out of it is that Struts uses standard J2EE mechanisms (Servlets, JSTL-EL, etc...) and WebWorks often does not. That's fine, but to try to spin it that these mechanisms are somehow bad seems a bit odd.

I disagree with you on this point. The only place where WebWork is less standard than Struts is in regard to JSTL. WebWork prefers OGNL over JSTL though you could always use the latter if you really want. Other than that WebWork is every bit as standards compliant as Struts... the WebWork team just doesn't believe in being explicitly dependent on Servlets/JSP even though that is the technology that the majority of XWork/WebWork projects will run on.

Originally posted by Jason Menard:
Overall, it looks like just a piece of marketing attempting to convince people to use their product instead of the de facto standard.

Of course this is exactly what it is. However, this doesn't mean that there is no techinical merit to the arguments present... because there is.