Re: Creating new EOObjectStoreCoordinator for thread
Re: Creating new EOObjectStoreCoordinator for thread
- Subject: Re: Creating new EOObjectStoreCoordinator for thread
- From: netBrackets <email@hidden>
- Date: Wed, 06 Aug 2008 14:05:34 -0500
Yep, that's what I did, as well as removing the offending "inverse" relationships. I changed to the ERXEC.newEditingContext originally to get rid of the "you don't have a delegate" error. What I didn't try was adding the "inverse" relationships back in while using ERXEC to create the new editing context, since for now I don't use the inverse links anyway. I may need them in the future though so might be interesting to add them back and see what happens. I'll let you know.
Jeff
On Wednesday, August 06, 2008, at 01:02PM, "Mike Schrag" <email@hidden> wrote:
>> Actually, I was using:
>>
>>>>>>> EOObjectStoreCoordinator parentObjectStore = new
>>>>>>> EOObjectStoreCoordinator();
>>>>>>> EOEditingContext threadEditingContext = new
>>>>>>> EOEditingContext(parentObjectStore);
>You're using Wonder, right? I just setup a test case of this and it
>worked fine, except that you should be using ERXEC to get your editing
>context:
>
> EOObjectStoreCoordinator coord = new EOObjectStoreCoordinator();
> EOEditingContext ec = ERXEC.newEditingContext(coord);
>
>Try that and see if it makes a difference.
>
>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