For most forms, you can probably get away with just using a DynaActionForm
and combining it with the Validator. I still use ActionForm subclasses for
really complex forms because of the control they provide. (I have a form with
two dimensional indexed properties plus mapped properties, all in one form,
plus complex validations). For most CRUD operations, however, I'd recommend
using DynaForms.
If you're looking at string-ified version of existing business objects, take
a look at FormDef (http://www.rabago.net/struts/formdef &
http://formdef.dev.java.net). Whether or not you use FormDef, though,
DynaForms work fine for a lot of cases, even those with indexed and mapped
properties and relatively basic validation.
The decision on which type of Action object to use should be made
independently of the type of form you use. Some prefer having related code
in the same action, others prefer the granularity of having one action class
per request. Either way works fine, and I personally haven't sensed a major
tendency towards one or the other from the users on this list. I myself use
MappingDispatchAction for actions I want to combine, and individual action
classes for complex actions (such as the handler of the form I described
above). The different dispatch action types have different pros and cons and
it's really up to you, your requirements and comfort level.
Just my opinion.
Hubert
--- Eric Noel <[EMAIL PROTECTED]> wrote:
> What is now the recommend technique for ActionForm, do we still have to
> use them? or just make use of the DynaActionForm instead and then create
> the corresponding Action or LookupDispatchAction?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
__________________________________
Do you Yahoo!?
Win a $20,000 Career Makeover at Yahoo! HotJobs
http://hotjobs.sweepstakes.yahoo.com/careermakeover
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
