• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Preventing an EOEditing context from being disposed
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Preventing an EOEditing context from being disposed


  • Subject: Preventing an EOEditing context from being disposed
  • From: Frédéric JECKER <email@hidden>
  • Date: Wed, 01 Jun 2011 14:11:25 +0200
  • Thread-topic: Preventing an EOEditing context from being disposed

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@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Follow-Ups:
    • Re: Preventing an EOEditing context from being disposed
      • From: David Avendasora <email@hidden>
    • Re: Preventing an EOEditing context from being disposed
      • From: Mike Schrag <email@hidden>
  • Prev by Date: Re: com.reportmill.base.RMException: Probable fatal error:No fonts found.
  • Next by Date: Re: Preventing an EOEditing context from being disposed
  • Previous by thread: Re: It's alive!
  • Next by thread: Re: Preventing an EOEditing context from being disposed
  • Index(es):
    • Date
    • Thread