No, it just means if you don't have to validate() (say because you are using
the struts validator) and you don't have to reset() (because you are using
the form in request all the time) and you are lazy (hey I use 'em) and don't
want to write the form with a bunch of getters and setters then they are
great.
The main different is that a hash map is used underneath and instead of
getAttributeName() you do get("attributeName") in the action to get the
values out. Then the only other thing to remember is to choose the right
one if you are using the struts validator (i.e. validating based on action
or based on form bean used for the action).
-----Original Message-----
From: Barry Volpe [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 04, 2003 5:18 PM
To: Struts Users Mailing List
Subject: When to use DynaActionForms?
The docs say:
DynaActionForms are meant as an easy solution to a common problem: Your
ActionForms use simple properties and standard validations, and you just
pass these properties over to another JavaBean (say using
BeanUtils.copyProperties(myBusinessBean,form)).
Does this mean for example I would not use DynaActionForms where I require a
form object in an Action that I am going to
use to populate a database?
If I require referencing a form object in an Action can I still use a
DynaActionForm?
Thanks,
Barry
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
