Hello Group,
I have been pointed to following URl to acquire MultiECLockManager class in
wiki and in some EC lock/ unlock issue discussion thread, but this link seems
to be broken, can any one provide me the latest stable version of this
file:http://wocode.com/cgi-bin/WebObjects/WOCode.woa/wa/ShareCodeItem?itemId=301Thank
You,Shravan Kumar. M-------------------------------------
--- On Wed, 4/8/09, Guido Neitzer <guido.neit...@gmail.com> wrote:
From: Guido Neitzer <guido.neit...@gmail.com>
Subject: Re: EOEditingContext Lock/Unlock best practice?
To: "shravan kumar" <mshravan_...@yahoo.com>
Cc: webobjects-dev@lists.apple.com
Date: Wednesday, April 8, 2009, 10:04 PM
On 7. Apr. 2009, at 23:43 , shravan kumar wrote:
> For setting the locking property mentioned, does my app need to extend
> ERXApplication? currently my app is very loosely coupled to Project Wonder
> i.e., we use different API's from Project Wonder as needed.
You need to extend from ERXApplication, ERXSession and use ERXEC exclusively
with:
ERXEC.newEditingContext()
whenever you create a new editing context. The session editing context is done
for you. All editing contexts are locked / unlocked for you.
> Moreover, after setting this property should I lock & unlock EOEditingContext
> in R-R loop or while fetching, saving, or modifying any EO object.
No. It happens automagically.
Just make sure you have no
new EOEditingContext()
calls anywhere in your call, replace all of those with the method mentioned
above to get an ERXEC.
cug
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
