Comments on: Apache Struts 2 development build http://www.samaxes.com/2006/10/20/apache-struts-2-development-build/ on technology Fri, 05 Dec 2008 07:43:39 +0000 http://wordpress.org/?v=2.5 By: Sourabh http://www.samaxes.com/2006/10/20/apache-struts-2-development-build/#comment-34 Sourabh Mon, 30 Apr 2007 11:19:21 +0000 http://samaxes.com/2006/10/20/apache-struts-2-development-build/#comment-34 what is this term : Stateful Checkboxes How to make Stateful Checkboxes How can we use Stateful Checkboxes There is no such info provided in any document if such a document found please supply the link Thanks Sourabh what is this term : Stateful Checkboxes
How to make Stateful Checkboxes
How can we use Stateful Checkboxes
There is no such info provided in any document
if such a document found please supply the link

Thanks
Sourabh

]]> By: david.alves http://www.samaxes.com/2006/10/20/apache-struts-2-development-build/#comment-33 david.alves Fri, 20 Oct 2006 11:26:56 +0000 http://samaxes.com/2006/10/20/apache-struts-2-development-build/#comment-33 One simple question... Is it more model driven?...or is it simply a great enhacement of the struts model? Struts is/was verbose, ok, but that was not the only thing that was wrong with it. Struts acts far away from the domain model, and doesn't integrate different domain-model driven components. For example in a traditional struts application using Hibernate, simple validation has to be defined two to three times (one in the validator.xml, one in the DB with contraints, and possibly one in the ORM mapping file/ORM mapping tags, (ok you'll say the latest two can be combined but its still verbose)). In another subject are there new abstractions (other than request and session)? old struts really lacked that. A simple makeover of the struts model might make developing in struts more productive, but is light years away from the productiveness of other WebDev tools that integrate domain-driven components with a simple sintax, both inducing less code and less complex code. Just my €0.02. One simple question…
Is it more model driven?…or is it simply a great enhacement of the struts model? Struts is/was verbose, ok, but that was not the only thing that was wrong with it. Struts acts far away from the domain model, and doesn’t integrate different domain-model driven components.
For example in a traditional struts application using Hibernate, simple validation has to be defined two to three times (one in the validator.xml, one in the DB with contraints, and possibly one in the ORM mapping file/ORM mapping tags, (ok you’ll say the latest two can be combined but its still verbose)).
In another subject are there new abstractions (other than request and session)? old struts really lacked that.
A simple makeover of the struts model might make developing in struts more productive, but is light years away from the productiveness of other WebDev tools that integrate domain-driven components with a simple sintax, both inducing less code and less complex code.
Just my €0.02.

]]>