Thank you, Martin,

I have used ReuseIfModelsEqualStrategy and the validation message side of it
work but now I have a different problem.

When I navigate away from the form panel, update the list of objects and
navigate back to the FormComponentPanel that holds the RefreshingView, only
one item from the list gets displayed.

I use a ListModel to pass the list of objects to the FormComponentPanel.

When used for the first time, the RefreshingView calls getItemModels() and
populateItem(), but after updating the ListModel, RefreshingView only calls
getItemModels() and *not* populateItem(). 

Would you happen to know why that is?

If I use DefaultItemReuseStrategy.getInstance() then  getItemModels() and
populateItem() get called every time. But that just takes me back to square
1.

I'm not sure if this is relevant. ReuseIfModelsEqualStrategy documentation
states that " the model and not the model object needs to implement the
Object.equals(Object) and Object.hashCode() methods".

I'm terribly sorry but I'm not sure completely understand that statement.
Would that be something to do with the RefreshingView not displaying all
items in the list model.

On trying to interpret that statement, on RefreshingView.getItemModels(), I
return an anonymous class that extends ModelIteratorAdapter. And on
ModelIteratorAdapter.model, I return an custom Model with extends Model<My
Application Object>. It is there that I implement hashcode and equals. But
the problem still persists.

I hope I'm not making things more confusing by writing extensively, but I
just wanted to put it out there, in case there was something simple and
small that I am missing.

Thanks in advance,
Lucas




--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/validation-in-form-component-panels-in-RefreshingView-tp4669068p4669081.html
Sent from the Users forum mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to