On Jul 3, 2008, at 8:00 PM, Lachlan Deck wrote:
On 04/07/2008, at 9:53 AM, Chuck Hill wrote:
If not what does lock() on the EC actually lock ?
It prevents changes in other ECs from affecting what is happening
in the locked EC. The changes are queued and processed when the
EC is unlocked.
If so, shouldn't rest of EC (waiting to save changes) just hang
around and wait instead of trying to access DBcontext and throw
exception? In other words, the exception we are seeing implies
that rest of ECs have no idea there is ec out there locked the
DBcontext.
No, that is just a badly worded exception. What it really means is
Called objectForGlobalID() on the databaseContext's active
editingContext,
[EMAIL PROTECTED], and
got back null. The object
: Researcher:(Active_Name=Peter Newnam {rowID=28082;}, is in
editing context
[EMAIL PROTECTED]
I've seen this happen when attempting to localize an object into
another ec fails... and you find out when attempting to save changes.
e.g., using some context that wasn't properly locked.
I don't think I recall having seen this. How would that happen?
localInstance using faulting so I can see it resulting in a dummy
fault EO possibly, but not an object in a different EC. Do you have
any more details on this?
Chuck
--
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
