Re: EOEditingContext Lock/Unlock best practice?
Re: EOEditingContext Lock/Unlock best practice?
- Subject: Re: EOEditingContext Lock/Unlock best practice?
- From: David LeBer <email@hidden>
- Date: Thu, 9 Apr 2009 16:05:26 -0400
On 9-Apr-09, at 3:58 PM, Guido Neitzer wrote:
On 9. Apr. 2009, at 12:46 , shravan kumar wrote:
Now am using ERXEC.newEditingContext() for creating new EC's,
manually locking/ unlocking where required. Also locking/ unlocking
in awake/ sleep respectively respect object bindings in the
component.
As long as you don't subclass ERXApplicaton and ERXSession, that
won't help you much over using EOEditingContext.
You might grap the code related to autolocking and incorporate that
in your app, but I'd avoid that.
If you want to use MultiECLockManager - unfortunately I never used
it and I don't have a download source. The links here:
http://wiki.objectstyle.org/confluence/display/WO/EOF-Using+EOF-Context+and+Database+Locking
Seem to be dead again (wocode).
I'm not sure if this up to date (and I don't use it), but I put the
copy I had here: <http://codeferous.com/files/MultiECLockManager.java>
;david
--
David LeBer
Codeferous Software
'co-def-er-ous' adj. Literally 'code-bearing'
site: http://codeferous.com
blog: http://davidleber.net
profile: http://www.linkedin.com/in/davidleber
twitter: http://twitter.com/rebeld
--
Toronto Area Cocoa / WebObjects developers group:
http://tacow.org
_______________________________________________
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