One of them is how to bookmark a page in Struts (which uses Actions. I would have a hard time explaining it until you were comfortable w/ Actions; else you would get confused).
Your other answer is: Struts uses Action, in action you must decide what page to forward to. (Never, ever, ask for a page, always ask for an action).
So the user asks for action. Action find out how much data there is, and forward to the right place, pre populating known information.
hth, .V
David Thielen wrote:
Hi;
I am designing a store check-out process. The old software (pre-struts) had a check at the top of each page to make sure the information from the previous page had been entered. And if not, forwarded to that page. So if you bookmarked the last page and went there, you would get forwarded back page by page and still start on the first page.
For my new system (using struts), what's the suggested process:
1.. Something like that? Only to be real struts-like I would need to have it go to a page that immediately called an action to see if all data needed for that page was there yet. 2.. Keep a single url so they cannot go to any page other than the first, then the second, etc. In this case, going back in the browser and then clicking reload would take them back to the page they were on. 3.. Just do the standard struts action when they submit a page and in that action go back to the first page for which I have incomplete information. So they can bookmark and click the "purchase" submit but it would then take them back to the first page of the checkout process.
So, what's standard out there?
thanks - dave
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
