Mike,

That sounds all too familiar to me. We are experiencing errors just like that. 
We have a feature that creates nested editing contexts several levels deep and 
fetches EOs all the way down to the bottom. Do you know of a workaround, patch 
or some way to recover from the bug you mention? I seem to remember a similar 
bug years ago in the days when EOF kept strong references. We are using Wonder.

Sorry for selfishly jumping in. Disappearing snapshots are causing us lots of 
pain because whole instances of our application become useless.

--
James
________________________________________
From: [email protected] 
[[email protected]] On Behalf Of 
Mike Schrag [[email protected]]
Sent: 25 March 2010 20:20
To: Marc Guenther
Cc: [email protected]
Subject: Re: Snapshots mysteriously vanishing?

>> by any chance was this an EO in a parent editing context that also existed 
>> in a child editingcontext?
>
> I don't think so, but I'm not sure. That particular EO could have been in all 
> differents ECs at the time, as it's entity is used all over the place.
>
> Do you have anything specific in mind?
yeah, there's a bug with refcounting of eo's in child ec's if the parent ec 
copy of the EO gets garbage collected ... the result of this bug is 
disappearing snapshots. this specifically applies to eo's fetched into a child 
that were already fetched into the parent, though, not to peer ec's.

ms
 _______________________________________________
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/jbrook%40upcbroadband.com

This email sent to [email protected]
 _______________________________________________
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]

Reply via email to