>Not really... your way you have to add the code to the action to do the validation and extraction as well as the JSP, model and SQL.
Model and SQL is not necessarily (and often) true: if I used course grained strategy, it may be that I've already got the field in my model, and if I use CMP EJB, I don't have to touch the SQL, because what it is returned to me is a local interface reference, rather than a ResultSet. And if I designed carefully my EJBs, and the field is already in the database, I wouldn't change a comma of my business model. So, resuming: I need another field in my presentation view (supposed I've got it already in my business model...): I add it to the JSP page, check it with Javascript, add its management to the servlet and I'm done. With Struts Actions: I add a field to the JSP, to the form object, dynamic or not (in case of an Action object getter/setter, reset() and validate() method), to the validation framework, to the Action (for its management)... The ActionForm way. I >change the JSP, the Form, The model and the SQL. If I'm using Dyna Forms then the only code I touch is the VO. Everything else is handled in config files. If >I'm using Hibernate then I only have to worry about the field being in the database. >Which would you rather maintain, 1-20 lines of code , or 2-3 config files? I can't see how my solution could lead to 20 lines of code against 2-3 config files? Marco --------------------------------------------------------------------- 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]
