> The benefit of using DynaActionForm instead is in one of the following
two
> use cases:
>
> * If your ActionForm bean doesn't have a custom reset() or validate()
> method, you don't need to write your own form bean class at all -
> simply configure the properties in struts-config.xml.
>
> * If your ActionForm bean does have a custom reset() or validate()
method,
> those are the only ones you have to write -- no more time wasted with
> all the property getter and setter methods (have you ever done anything
more
> boring that writing those?). Simply subclass DynaActionForm and
> implement the validate() method in the usual way (although it will
> have to use get() to get the values to be tested, instead of the
> usual property getter methods).
>
> Given how many situations are covered by one or the other of the above,
> I'd say DynaActionForm is modestly useful :-). But, like most things,
> it's just an option.
>
> Craig
>
So why would anyone ever NOT use DynaBeans?
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
