Never did, but it seems the struts-example gives you some tips on that.
You can define a parameter action or phase that will hold the current phase
on the wizard. Since an Action can have multiple forwards, you can select
the next step based on what is the current one, if the user pressed cancel
or back.
On each interaction you will save a new transaction token on the session.
The form bean can be the same. Or it can be one for each step and then you
make the bookeeping of the user choices.
I think it is quite like that.
Wellington Silva
UN/FAO
-----Original Message-----
From: Todd Story [mailto:[EMAIL PROTECTED]]
Sent: Monday, June 04, 2001 4:29 PM
To: Struts-User (E-mail)
Subject: Wizard form approach
Is anyone currently using multiple pages (same ActionForm) in a wizard-esque
manner? If so, how are you doing validation without knowing the details of
which elements are displayed on which page? In other words I'd like some
fields to be required without having the user to go back 3 pages. Thanks.
