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 get ComponentNotFoundExceptions either.
Have fun
Sven
On 17.12.2015 09:35, Patrick Davids 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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
