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
: 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
: 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
of model object changes can be guaranteed.
-Original Message-
From: Igor Vaynberg [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 31, 2008 6:16 PM
To: users@wicket.apache.org
Subject: Re: Component#modelChanging and Component#modelChanged when
IModel#setObject
well, it notifies if the model
.
-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
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
To: users@wicket.apache.org
Subject: Re: Component#modelChanging and Component#modelChanged when
IModel#setObject
What would happen if more than one component uses the same model? Would
we keep a list of components to notify? If that's the case why not just
implement listeners instead, so
