> Using your example I would have a form to gather the search criteria. > Submitting the form to the first action would gather a list of employess and > store that list in a request scope attribute. It would then forward to the > employee list jsp which would render the list of employees. Selecting an > employee would make a request to another action (without using an ActionForm > at all), which would create a request scope attribute containing employee > details, and forward to the details page which would show the details > contained in the new employee detail attribute.
True, but your solution is victim of the "example is always simplest in the book" symptom. In order to select a single employee, there are more than 8 parameters that need to be tracked...hence why I suggest the output form. What would be ideal is if ActionForms could be used with links, automatically tacking on the elements from the form. I guess the short term solution would be to place the form in session to begin with, and then just update it with the new information from each submit, automatically carrying over the "excess" that remains the same each time. Dan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
