EO's have a strong reference to their EC, so if you have a strong reference to an EO, you implicitly have a strong reference to its EC, which means it won't be GC'd ... you sure you didn't actually dispose the EC that fetched those objects?
On Jun 1, 2011, at 8:11 AM, Frédéric JECKER wrote: > Hi list, > > My app uses a singleton object to manage communication with third party app. > In order to save some database queries, this singleton statically "caches" > some simple EO's within an NSArray. > > This works pretty well except that sometimes I encounter such messages : > java.lang.IllegalStateException: Attempt to send message to an object after > its editing context was disposed > > Digging the stacktrace made me think that the cached EO's EOEditingContext > has been eaten by the garbage collector. > Is there a way to avoid this ? > > Regards > > Fred > _______________________________________________ > 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/mschrag%40pobox.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]
