Re: IllegalStateException: "...EOEditingContext has already been disposed"
Re: IllegalStateException: "...EOEditingContext has already been disposed"
- Subject: Re: IllegalStateException: "...EOEditingContext has already been disposed"
- From: Philippe Rabier <email@hidden>
- Date: Thu, 29 Sep 2016 15:32:21 +0200
On 29 sept. 2016, at 12:18, Paul Hoadley < email@hidden> wrote:
When do you dispose of the EC?
I don’t formally dispose of it. I just let it eventually fall out of scope and get GC’d. Is that a bad idea?
No but seems the right thing to do. I was just trying to understand how it was getting a null editing context
When should you normally explicitly dispose() an EC? That’s really not something I do very much of at all.
It helps to free up memory sooner than waiting for GC. I used it in the RR loop or when you have a big number to objects to manipulate (export job or whatever) if you can’t do raw sql. Rather than having a single ec, you can can dispose and create a new one every batch of x EOS. I used this piece of code all the time:
EOEditingContext ec = newEditingContext(); ec.lock(); try { ... } catch (Exception e) { log.error("method: blabla ", e); } finally { ec.unlock(); ec.dispose(); }
Best,
Philippe
|
_______________________________________________
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