well, it notifies if the model is changed through the component. there is no way for us to really intercept a setobject call on an arbitrary model instance, figure out which components it is currently attached to, and call modelchanging methods on them.
-igor On Thu, Jul 31, 2008 at 3:08 PM, Hoover, William <[EMAIL PROTECTED]> wrote: > Well, I am still trying to hash that one out- any ideas? > > I just think that if there is a method that indicates that it will be > called anytime that a model is changing that it should follow through > with that contract. > > -----Original Message----- > From: Igor Vaynberg [mailto:[EMAIL PROTECTED] > Sent: Thursday, July 31, 2008 6:01 PM > To: users@wicket.apache.org > Subject: Re: Component#modelChanging and Component#modelChanged when > IModel#setObject > > how should we handle that? > > -igor > > On Thu, Jul 31, 2008 at 2:43 PM, Hoover, William <[EMAIL PROTECTED]> > wrote: >> Seems strange that Component#modelChanging and Component#modelChanged >> are never called when IModel#setObject is called... >> >> https://issues.apache.org/jira/browse/WICKET-1764 >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
