I first thought that the EO's where fetched using a dedicated EOEditingContext but digging the code led me to a special case where those could be
Fetched using a disposable context.
I changed the code so that those EO's are fetched using a dedicated EOEditingContext on which a reference is kept so that it won't get disposed
De : Mike Schrag <
email@hidden>
Date : Wed, 1 Jun 2011 08:39:27 -0400
À : David Avendasora <
email@hidden>
Cc : Frédéric JECKER <
email@hidden>, WebObjects-Dev Mailing List List <
email@hidden>
Objet : Re: Preventing an EOEditing context from being disposed
The EOF documentation () gives this tip to create strong references from the EC to the EO, but I don't think that's going to change things, but I don't think it could hurt either in this situation:
"You can force an EOEditingContext to hold strong references to all of its EOEnterpriseObjects by invoking either setInstancesRetainRegisteredObjects or setRetainsRegisteredObjects on an editing context in which no enterprise objects are registered."
yeah that's the other direction ... it won't matter here.
ms