> -----Original Message-----
> From: Dan Allen [mailto:[EMAIL PROTECTED]
> Sent: Thursday, August 19, 2004 12:18 PM
> To: [EMAIL PROTECTED]
> Subject: input and output form
>
>
> I often times run into the conflict, when developing a Struts
> application, of which form to choose for a given action. The scenario
> is such that one form is being populated by the request while the
> other form needs to be populated for the output. An example would be
> a sequence of pages describing an employee and his/her employment
> data. The first page might be a form to search for employees. The
> second page would display the employee. Finally, the third page might
> show the details of an employment. Each page has to lookup
> information and then prepare a form to display nested information.
>
> Which form to use? Perhaps Struts should have the concept of an input
> and an output form. Or is the solution just to split the action into
> two and then do an internal forward from one to the next in sequence.
You can do something like:
blah SearchForm blah {
blah searchField1;
blah searchFiled2;
Collection results;
blah blah
}
Read the fields, do the search, populate the resulting list. All in one form.. you
don't have to display every field in a form if you don't want to.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
