Yeah that scenario still makes sense where the user goes to the form page itself, but i was refering to the scenario where the user goes to the page (with the back button) which got shown after form submission, as in that case the browser would be submitting the request to the server (implicitly in case of a GET) and hence a double form submit OR the other scenario where user presses the refresh button on that previous page.
Farhan. Johan Compagner wrote: > > But a user can click the back button to go to the previous page with > the form and submit it again, but that isn't something wicket should > prevent. Because that could be valid for that application, a user > submit something then sees it made a mistake, presses back, corrects > it and submit again.. > > 2007/11/18, Eelco Hillenius <[EMAIL PROTECTED]>: >> > Yet another question... >> > >> > Does wicket handles double form submission in anyway ? like if the user >> > clicks the back button where the previous page was a result of a form >> > submission, which could result in double form submission..OR otherwise >> > refreshes that page.. >> >> Yes, Wicket by default uses the redirect after submit pattern. See the >> renderStrategy property of IRequestCycleSettings (read the Javadoc of >> the three available strategies). >> >> Eelco >> >> --------------------------------------------------------------------- >> 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] > > > -- View this message in context: http://www.nabble.com/double-form-submission-handling---tf4829048.html#a13818039 Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
