If the user is restricted to see the same data once use ASO or @Persist. It is no harm if you have a user fiddling with such a form and seeing the same data twice.
In filling out a lengthly multipage questionary about registration I would think of harmful behaviour using the same formular twice the same time. If not, stick to conversation (use an Id). Such a general conversation service with saving the conversation to db in a distributed system is almost every time the right thing to go to implement multi-page forms / wizards / workflows. Cheers, Martin (Kersten) -----Ursprüngliche Nachricht----- Von: Angelo Chen [mailto:[EMAIL PROTECTED] Gesendet: Montag, 10. März 2008 14:06 An: users@tapestry.apache.org Betreff: T5: persistency over several pages Hi, I have this registration module which consists several pages, user has to answer several questions for every page, and he can go to next/prev until the last page, then 'finish' button is clicked, how to persist those data across the several pages? any idea to implement something like this? Thanks, A.C. -- View this message in context: http://www.nabble.com/T5%3A-persistency-over-several-pages-tp15950732p15950732.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
