The order of calls is: takeValueForKey -> setXXX -> takeStoredValueForKey
All of these maybe skipped except for takeStoredValueForKey, so that is the only one you should override to see what is getting saved. On Thu, Sep 11, 2014 at 8:55 AM, John Pollard <[email protected]> wrote: > Hi List, > > In some debugging within takeValueForKey() I want to find out if the key > already has a value set. If I call valueForKey() or storedValueForKey() and > the value isn't already set I get infinite recursion as it triggers a fault > and tries to load with takeValueForKey() and so on. > > I am trying to debug where a value is being set to null, but apparently > not going via validateXXX() or setXXX() methods, so I want to trap the case > where the takeValueForKey() is passed null when the key value was > previously non-null and log a stack trace. > > Thanks > John > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Webobjects-dev mailing list ([email protected]) > Help/Unsubscribe/Update your Subscription: > > https://lists.apple.com/mailman/options/webobjects-dev/johnthuss%40gmail.com > > This email sent to [email protected]
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
