Even if you want to control that, it could be done within the setModel() method. After all, that's exactly what is done for wrapOnAssignment. Why not apply the same logic to wrapOnInheritance ?
Jan Eelco Hillenius wrote: > > Theoretically, people can manually set model to null after the > component had it's own model first. But that would be quite weird. > > Eelco > > -- View this message in context: http://www.nabble.com/Performance-problems-due-to-Component%3AinitModel%28%29-tf3362476.html#a9360990 Sent from the Wicket - Dev mailing list archive at Nabble.com.
