to EOeditingContext.processRecentChanges()
will trigger the actual processing of such delete rules.
Pierre
Tom Woteki [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
01/15/2006 06:33 PM
To
webobjects-dev@lists.apple.com
cc
Subject
refreshing and relationships
I'm stumped. I guess I'm
Dev WO [EMAIL PROTECTED]
01/16/2006 12:50 PM
To
[EMAIL PROTECTED]
cc
Tom Woteki [EMAIL PROTECTED],
webobjects-dev@lists.apple.com, [EMAIL PROTECTED]
Subject
Re: refreshing and relationships
Hi Pierre,
I've red the API about processRecentChanges(), but I still
have a question
On Jan 15, 2006, at 12:33 PM, Tom Woteki wrote:
I have a source object, sourceObj, with a to-many relationship. Say
the relationship key is targets . I obtain the related objects by
invoking sourceObj.targets() where the method targets() returns an
NSArray as a cover for a call to
I don't think I should have to do this. But to your point, I am trying to get a "fresh array". What I want, and expected, is that any invocation of "targets()" subsequent to deleting a target object should deliver that fresh array. What I don't understand is why it isn't happening the way I
That doesn't seem to work. I tried it before and/or after the call to
deleteObject and in conjunction with invoking refreshObject on the
owning sourceObj. No combination seems to work.
Thanks
Tom
On Jan 15, 2006, at 1:29 PM, Arturo Pérez wrote:
On Jan 15, 2006, at 12:33 PM, Tom Woteki
Hi Tom,
did you try Arturo's tip?
Regarding what I gave you, you've got to call the NSMutableArray in
your WOComponent that display the list and no more the object's
relationship.
As far as I understand it, the relationship doesn't display the
expected array because the relationship
