Lets work out a diagram that explains the flow,
Tokens should be able to do this..
if there is both a SaveXXXAction and EditXXXAction for all JSP accessed,
Action JSP Page
EditPage1 Set Token
Page 1
SavePage1
CheckToken if valid
Forward -> go to EditPage2Action
Redisplay ->setToken, forward to Page1.jsp
Save
EditPage2 SetToken
Page2
SavePage1
CheckToken if valid
Forward -> go to EditPage3Action
Back ->Forward to EditPage1Action
Redisplay ->setToken, forward to Page2.jsp
Save
EditPage3Action SetToken
Page3
SavePage3Action
CheckToken if valid
Back ->Forward to EditPage2Action
Redisplay ->setToken, forward to Page3.jsp
Save
If there are any holes in this they can be plugged, such as
going between SavePage2Action -> EditPage1Action;
Based on the struts example usually the request parameter
named 'action' can be "Create", "Edit", "List", "ListSubset",
we also use a value of "InProcess" which means that this
Wizard page has already been accessed before.
-Rob
Nathan Coast wrote:
> Hi,
>
> In the site I'm developing, there are sections that have forms on consecutive
> pages, I want to guarantee that pages are navigated: page1 -> page2 -> pageN.
> At the same time allowing back and forward navigation to change values entered
> on previous pages. After the last submit, the only valid page in the sequence
> is then page1. I've had a look at the Struts Token functionality but I don't
> think it can support this functionality. Is it possible with Tokens or some
> other way?
>
> Thanks in advance
> Nathan
--
Robert Leland [EMAIL PROTECTED]
804 N. Kenmore Street +01-703-525-3580
Arlington VA 22201
