Re: ERXEC and methods getting called without lock
Re: ERXEC and methods getting called without lock
- Subject: Re: ERXEC and methods getting called without lock
- From: Daniel Eggert <email@hidden>
- Date: Fri, 5 Aug 2005 12:47:29 +0200
On Aug 5, 2005, at 12:25 PM, Anjo Krank wrote:
You still have to lock the EC before using it. ERXEC just prevents
leaving locked EC afters the RR loop. However, you can also set the
autoLock stuff to on
er.extensions.ERXEC.defaultAutomaticLockUnlock=true
in which case the EC will get automatically looked. As this can
lead to deadlocks I normally don´t recommend it, though.
Cheers, Anjo
That makes sense, then. I read the documentation <http://
wonder.sourceforge.net/javadoc/er/extensions/ERXEC.html> as if
locking always was done automatically.
The obvious question is: If ERXEC does not do auto-locking (i.e.
er.extensions.ERXEC.defaultAutomaticLockUnlock=false) does it still
provide any advantage over EOEditingContext?
Or put differently: Does combining ERXEC and MultiECLockManager
<http://wocode.com/WOCode/Files/MultiECLockManager.java> make any sense?
/Daniel
_______________________________________________
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