Hi! I think Wicket Ajax should prevent this on the client side. As a workaround you can disable the sumbit button from javascript event handler and re-enable it from wicket ajax response.
2011/2/28 eugenebalt <[email protected]> > How do we prevent the user from double-clicking a non-Ajax component? > > When the submit occurs, isEnabled is set to "false" for the Wicket Button. > If the user does a quick double click on the button, its throws a wicket > runtime excpetion saying the component is disabled. > > Thanks > > -- Zoltán Nagy
