Hi, our first Wicket-based application is about to go into testing and I'm feeling rather uncomfortable about the fact that I don't really understand what happens when user uses browser's back button and then submits some 'outdated' form. Can someone elaborate please on what exactly happens when Wicket receives submit from the 'old' page?
On a more specific note, I will most probably need to block user from submitting the same form more than once. E.g.: - If I wanted to prevent user from using back button at all, how would I determine that the incoming submit is from the 'old' page? - If I determined that Wicket received submit from the 'old' page, how would I send user back to the last 'valid' page they were on? - If I wanted to detect that user submits the same form twice (without necessarily blocking the back button in all cases), how would I go about it? I suppose I could store something in Session to track which forms were already submitted? P.S. Sorry for kind of 'reposting' my previous question, but I'm running out of time on this project and really would love to understand how to properly handle browser's 'back' button... --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
