EOCustomObject valueForKey avoiding infinite recursion

2014-09-11 Thread John Pollard
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

Re: maven.wocommunity.org is down

2014-09-11 Thread Dennis Bliefernicht
Hi everyone, unfortunately the maven.wocommunity.org has gone down (Service unavailable), at least since yesterday we could observe this issue. Greetings Thanks for providing the repo / fixing this in advance :-) Dennis ___ Do not post admin

Re: EOCustomObject valueForKey avoiding infinite recursion

2014-09-11 Thread Ray Kiddy
On Thu, 11 Sep 2014 14:55:16 +0100 John Pollard j...@pollardweb.com 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

Re: EOCustomObject valueForKey avoiding infinite recursion

2014-09-11 Thread John Huss
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 j...@pollardweb.com wrote: Hi List,

Re: maven.wocommunity.org is down

2014-09-11 Thread Henrique Prange
Hi Dennis, Thanks for reporting. The service is back up. Cheers, Henrique On 11/09/2014, at 12:27, Dennis Bliefernicht dennis.blieferni...@xyrality.com wrote: Hi everyone, unfortunately the maven.wocommunity.org has gone down (Service unavailable), at least since yesterday we could

Re: EOCustomObject valueForKey avoiding infinite recursion

2014-09-11 Thread John Pollard
Ray, Thanks for the thought. I do want to log the stack trace but as I can't predict when this issue might happen and it is rare. I want to narrow down to the close circumstances first, or else I will be logging thousands of these stack traces in normal operation when there isn't a problem.

Re: EOCustomObject valueForKey avoiding infinite recursion

2014-09-11 Thread John Pollard
Apologies, I meant takeStoredValueForKey(). Within there, how can I safely see what the value currently is when when this method is called, before I invoke super. takeStoredValueForKey() to take on the new value? John On 11 Sep 2014, at 18:10, John Huss johnth...@gmail.com wrote: The order of

Re: EOCustomObject valueForKey avoiding infinite recursion

2014-09-11 Thread Theodore Petrosky
I have used the @Override public void willUpdate() { )method then I get the original value and compare it if (committedSnapshotValueForKey(PROJECT_DESCRIPTION_KEY) != NSKeyValueCoding.NullValue) {

Re: EOCustomObject valueForKey avoiding infinite recursion

2014-09-11 Thread Chuck Hill
That might not give you what you want. committedSnapshot is set when the object is first mutated. If you if the value is changed like: null - B - null Then this won’t log what is desired. Chuck On 2014-09-11, 12:28 PM, Theodore Petrosky wrote: I have used the @Override public void

Re: EOCustomObject valueForKey avoiding infinite recursion

2014-09-11 Thread Chuck Hill
You are going to grow hair on your palms doing this but… willRead(); Object value = __dictionary().valueForKey(“your attribute”); Should, I think, do what you want. Of course, it is package protected so you will need to use reflection to get access. And the result may be null if the object