Eelco Hillenius wrote:
>
>> Lets say that we wanted to do "sophisticated clustering", so we use the
>> ONE_PASS_RENDER option. However, we still want to avoid the double-submit
>> problem. Is it possible? Is there a way the application can prevent it
>> from
>> happening in this case?
>
> Sure. Use custom solutions, like the one Igor suggested.
>
I think I understand -- we can use exactly the same solution to the form
re-submit problem in the case of [a back-button navigation followed by a
form re-post] to solve the double-submit problem in the case of [a page
refresh after a form post when ONE_PASS_RENDER is being used].
In both cases, if we subclass Form and hold state to track whether the form
has already been submitted once before, we can handle the problem the way
Igor suggested previously. Is that correct?
--
View this message in context:
http://www.nabble.com/double-form-submission-handling---tf4829048.html#a13860852
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
