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: Anjo Krank <email@hidden>
- Date: Fri, 5 Aug 2005 13:31:03 +0200
Am 05.08.2005 um 12:47 schrieb Daniel Eggert:
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?
a) using a ERXEC as a factory very much makes sense and you can
switch your own subclass without any changes to Wonder code. (which
was what ERXEC first was all about)
b) using ERXEC as a class (ie the actual EC you get from the factory)
makes a lot of sense as it auto UNlocks after the RR loop - which
just happens and is not really under your control. You can't use D2W
without it.
c) you *can* use the auto LOCK features, but I never tried it,
wouldn't recommend it and using them is generally sloppy. Fix your
code instead.
Or put differently: Does combining ERXEC and MultiECLockManager
<http://wocode.com/WOCode/Files/MultiECLockManager.java> make any
sense?
No, as the unlock mgmt. is handled by ERXEC anyway.
Cheers, Anjo
_______________________________________________
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