Re: Why is Component.setDefaultModelObject() checking for equality before setting ?

2010-07-23 Thread Joseph Pachod
Igor Vaynberg wrote: the added value is that if wicket detects that the set is a noop because the objects are the same it doesnt need to create a new version of the page. ok, makes more sense :) I was quite a surprised though, I had not heard of it at all even read all these wicket books an

Re: Why is Component.setDefaultModelObject() checking for equality before setting ?

2010-07-21 Thread Igor Vaynberg
the added value is that if wicket detects that the set is a noop because the objects are the same it doesnt need to create a new version of the page. -igor On Wed, Jul 21, 2010 at 8:25 AM, Joseph Pachod wrote: > hi > > I was surprised to see, in Component.setDefaultModelObject(), the following >

Why is Component.setDefaultModelObject() checking for equality before setting ?

2010-07-21 Thread Joseph Pachod
hi I was surprised to see, in Component.setDefaultModelObject(), the following code: // Check whether this will result in an actual change if (!getModelComparator().compare(this, object)) { modelChanging(); model.setObject(object); modelChan