Hi,
well, t:saveState should exactly fit your needs in this case and it
doesn`t come with any burden.
Just use it in your wizard page like this:
t:saveState value=#{yourWizardPageBean}/
The yourWizardPageBean then is a kind of representation of the whole
wizard steps.
For instance, you can
inside of trinidad, there is also a pageFlowScope
-M
On 11/18/06, Andrew Robinson [EMAIL PROTECTED] wrote:
Conversational state is made for this type of work. There is one in
the sandbox (haven't used it). JBoss-Seam is excellent for
conversations (what I used). Also the shale framework has a
One way is to use the tomahawk saveState control. Use a single request level
bean to collect your form data. Save the bean use saveState in each page of
the wizard. If the user wants to cancel use an action which either navigates
to a page where there is not saveState (the wizard backing bean is
Conversational state is made for this type of work. There is one in
the sandbox (haven't used it). JBoss-Seam is excellent for
conversations (what I used). Also the shale framework has a dialog
manager that can do something similar I think.
Other than that, use t:saveState or a4j:keepAlive
4 matches
Mail list logo
