I meant disabling all page components (maybe with additional animation)
until answer arrives from the server.
Tomer
Igor Vaynberg wrote:
> you can still do it via an attribute modifier. but i think we should
> remove final from those link methods anyways.
>
> what o you mean by "locking" ?
>
>
you can still do it via an attribute modifier. but i think we should remove final from those link methods anyways.what o you mean by "locking" ?-igorOn 11/5/06,
Tomer Mevorach <[EMAIL PROTECTED]> wrote:
I prefer not to synchronize it on the server side.The thing that bothers me is that there is no
I prefer not to synchronize it on the server side.
The thing that bothers me is that there is no way to add JS code to the
onclick event of the submit button, therefore i am using forms onsubmit
event for disabling the button.
by the way, is there any built in mechanism in wicket for locking the
Sorry, synchronized *on* the session.
Eelco
On 11/5/06, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
> It shouldn't though. Requests to pages are synchronized throughout the
> session, so if you want to block a second request, just disable that
> link/ ignore the second request e.g. by setting a va
It shouldn't though. Requests to pages are synchronized throughout the
session, so if you want to block a second request, just disable that
link/ ignore the second request e.g. by setting a variable on your
form).
Eelco
On 11/5/06, Tomer Mevorach <[EMAIL PROTECTED]> wrote:
> when using a SubmitLi
when using a SubmitLink, double click on the submit button results in
submitting the form twice.
submitting the form twice results in in unwanted behavior (in some
cases, when markup hierarchy changes between submits, it results in a
RuntimeException).
however, there is no way to update onclick
