> The one missing piece from your solution is synchronization. There is the > slightest possibility that the second submit of a double submit could enter > onSubmit before the token is reset. I am not yet sure what would be the best > object to synchronize on, possibly the session id? >
Actually wicket already synchronizes on the session so there won't be a problem with a second commit executing before the first has finished. Maurice --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
