Re: Why do Dynamic Elements get values from enclosing component in takeValuesFromRequest?
Re: Why do Dynamic Elements get values from enclosing component in takeValuesFromRequest?
- Subject: Re: Why do Dynamic Elements get values from enclosing component in takeValuesFromRequest?
- From: Karthik N <email@hidden>
- Date: Thu, 26 Feb 2009 06:28:49 -0800
hi,
yes absolutely - i tried some experiments and the get() gets called before the set() whenever the values change.
here's what's puzzling me - i find that when the value doesn't change the get()'s never called!
for WO to know that the value has changed it would have to fire a get() every time wouldn't it?
is WO bypassing the get() and inspecting the underlying private String userName instead for changes and then calling the get()/set()?
Thanks, Karthik
On Wed, Feb 25, 2009 at 7:06 PM, Mike Schrag
<email@hidden> wrote:
Why is there a necessity for the WOTextField to actually get() values from the enclosing component in a takeValuesFromRequest() stage of the request-response cycle?
validateTakeValueForKeyPath only pushes the value if it is different than the previous value (or if the previous or new value is a null), which requires getting the previous value first
ms
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden