Is there any disadvantage of to letting a DispatchAction handle both the
setup and submission of a form something like the following:
DispatchAction contains the following methods:
1. init() - sets up the form with initial values for select lists, etc.
2. submitForm() - handles the validation
On Fri, Jul 18,'03 (09:22 AM GMT-0400), Witbeck, wrote:
Is there any disadvantage of to letting a DispatchAction handle both
the setup and submission of a form something like the following:
DispatchAction contains the following methods:
1. init() - sets up the form with initial values
On Fri, Jul 18,'03 (10:49 AM GMT-0400), Rick wrote:
1. init() - sets up the form with initial values for select lists,
etc. 2. submitForm() - handles the validation and data associated
with the completed form setup above and forwards to another
DispatchAction's init() method.
I do
]
Sent: Friday, July 18, 2003 10:52 AM
To: Struts Users Mailing List
Subject: Re: DispatchAction role
On Fri, Jul 18,'03 (10:49 AM GMT-0400), Rick wrote:
1. init() - sets up the form with initial values for select lists,
etc. 2. submitForm() - handles the validation and data associated
4 matches
Mail list logo
