im not sure why it doesnt call onmodelchanging(). it should, looks like a bug. but it does make the page dirty by calling addStateChange().
-igor On Wed, Mar 28, 2012 at 4:04 AM, Martin Grigorov <[email protected]> wrote: > Hi, > > Is there a reason why org.apache.wicket.Component#setDefaultModel() > doesn't call modelChanging() at the top of its body ? > It calls modelChanged() at the bottom. > > org.apache.wicket.Component#setDefaultModelObject() calls them both, > as I'd expect. > > I'm asking this because org.apache.wicket.Component#modelChanging() > the important one, it makes the page dirty. > > -- > Martin Grigorov > jWeekend > Training, Consulting, Development > http://jWeekend.com
