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
where pageLoadingFrame is just a custom blocking logic.
On Thu, Dec 17, 2015 at 10:02 AM, Ernesto Reinaldo Barreiro <
reier...@gmail.com> wrote:
> Use a veil to block screen while AJAX is bussy.
>
>
> Wicket.Event.subscribe('/ajax/call/before', function(jqEvent, attributes,
> jqXHR, errorThrown,
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,
Hi,
>Is it quite save to use the ReuseIfModelsEqualStrategy?
>What are the pitfalls using it?
as long as you follow the instructions in its JavaDoc I see no problem
in using this strategy.
Why are you refreshing the whole table instead of a single row only? If
you did the latter, you won't
Hi Sven,
> Why are you refreshing the whole table instead of a single row only?
At the end of the table is a ButtomToolBar calculating sums of all rows.
(the Spinner is for changing amounts / prices for an item in the rows)
How can I refresh a single row? This would help a bit (than, later, I
