On Thu, Jul 3, 2008 at 9:51 AM, Matej Knopp <[EMAIL PROTECTED]> wrote: >> >> And there is some functionality in there that Wicket might >> be better without. For example, onModelChanged / Changing >> things become tricky when you share the same model between >> different instances. And when using setModelObject() with an >> object that is equal to the current model object, but a >> different instance (such as a Hibernate-persisted object >> bound to the correct session), you have to either do >> getModel().setObject() or change the model comparator. >> > > setModelObject isn't the best idea IMHO. Models should support some > kind of state change notifications, we might want to improve that for > 1.5, though it probably wouldn't be very easy to do. Well, we can hardly detect change of propertypromodels unless we pull and compare the value every time... > > -Matej >
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
