Lists

Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists

Re: Strange localInstanceOfObject behaviour...

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Strange localInstanceOfObject behaviour...

Subject: Re: Strange localInstanceOfObject behaviour...
From: "Jerry W. Walker" <email@hidden>
Date: Thu, 1 Jun 2006 06:52:12 -0400

Hi, Mark,

On May 31, 2006, at 5:35 PM, Mark Ritchie wrote:

localInstanceOfObject() uses EOEditingContext's faultForGlobalID() method. faultForGlobalID() should find a new, unsaved EO's which are: 1) registered in the receiving EOEditingContext 2) registered in the attached shared EOEditingContext 3) registered in a parent object store (Note: I say should because I'm not sure about case #2. I have code to demo cases 1 and 3 which I wrote to answer a similar question at WWDC last year. I may have even posted it to the list but I'm not sure if it got cleaned up for that. ;-)

I was the one who asked the question at WWDC (2005) for which you created these code examples and I would love to see them if you've finished them.

Regards,
Jerry

-- __ Jerry W. Walker, WebObjects Developer/Instructor for High Performance Industrial Strength Internet Enabled Systems

    email@hidden
    203 278-4085        office

_______________________________________________
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



Prev by Date:
What is the best way to synchronize EOs between coordinators?

Next by Date:
Updated objects not present in updatedObjects() array ?

Previous by thread:
Re: What is the best way to synchronize EOs between coordinators?

Next by thread:
Re: Strange localInstanceOfObject behaviour...

Index(es):

Date
Thread