Use a veil to block screen while AJAX is bussy.

Wicket.Event.subscribe('/ajax/call/before', function(jqEvent, attributes,
jqXHR, errorThrown, textStatus) {
    pageLoadingFrame("show");
});

Wicket.Event.subscribe('/ajax/call/complete', function(jqEvent, attributes,
jqXHR, errorThrown, textStatus) {
    setTimeout(function(){
        pageLoadingFrame("hide");
    },500);
});

You can do that globaly as above...

On Thu, Dec 17, 2015 at 9:35 AM, Patrick Davids <
[email protected]> wrote:

> Hi all,
> I have a problem with an ComponentNotFoundExceptions when multiple
> ajax-request are fired with refreshing components and I fixed it using a
> ReuseIfModelsEqualStrategy in my refreshing DataTable.
>
> But I'm not sure about the consequences using ReuseIfModelsEqualStrategy.
>
> This is my case:
>         Panel
>                 DataTable
>                         (rows with columns)
>                                 Spinner with ajax-request refreshing the
> DataTable on change/spin
>
>
> The Spinner has an AjaxChannel.QUEUE not too loose any data, when the user
> does multiple fast clicks.
>
> Now the problem:
> If the user is very fast with the mouse and uses the Spinner of the next
> row in the DataTable, while the previous Spinner is still working on its
> AjaxChannel.QUEUE and always refreshes the DataTable I run into
> ComponentNotFoundExceptions, when the first click of the next used Spinner
> is occuring.
>
> Using ReuseIfModelsEqualStrategy for the DataTable, it is working, because
> the Items and componenents are reused.
>
> I never used the ReuseIfModelsEqualStrategy before and while reading the
> javadoc, I am not sure about the equals() details and if I understood it
> really, really right.
>
> Is it quite save to use the ReuseIfModelsEqualStrategy?
> What are the pitfalls using it?
>
> Thanx for any feedback and know-how!
>
> kind regards
> Patrick
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>


-- 
Regards - Ernesto Reinaldo Barreiro

Reply via email to