Ah yes, it occurred to me last night that my implementation of equals for my
object must be the problem, thanks for the help.
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Updating-inmethod-grid-from-the-server-tp3015007p3018162.html
Sent from the Users forum
to refresh a DefaultDataGrid.
All help is much appreciated
Adam
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Updating-inmethod-grid-from-the-server-tp3015007p3015007.html
Sent from the Users forum mailing list archive at Nabble.com
the old
model, regardless of whether the data in the new model is different.
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Updating-inmethod-grid-from-the-server-tp3015007p3016451.html
Sent from the Users forum mailing list archive at Nabble.com
On Wed, Oct 27, 2010 at 7:00 PM, Adz adam.dar...@three.com.au wrote:
I tried that, it didn't make any difference. I think the problem is due to
the item reuse strategy ReuseIfModelsEqualStrategy. It has a cache of the
existing items and only compares to see if the new models are in the list
