I agree there is no need.
It does not break anything to just start using ERXEC if you have
already integrated MultiECLockManager. The EC's just get unlocked
before the ERXEC automatic check-and-unlock at the end of the R-R, so
they don't get unlocked because they already are unlocked.
Sure enough, if you are deciding just now what scheme to use for R-R
lock/unlock, then pick one or the other. I just am not going to spend
time deleting or changing code and then testing code that works fine
just because I incorporated ERXEC's after I had the MultiECLockManager
implemented a year beforehand.
On Nov 20, 2005, at 11:52 AM, David Teran wrote:
Am 20.11.2005 um 14:37 schrieb Kieran Kelleher:
However if I use the
er.extensions.ERXApplication.useEditingContextUnlocker=true and
ditched MultiECLockManager, would I not have to then add a mechanism
for locking at session awake?? I recall a thread message from Anjo
Krank at one time saying to just lock/unlock ERXEC's yourself unless
you are using D2W ... I don't remember when..... but it influenced
There is no need for MultiECLockManager -and- unlocking stuff from
ERXEC. Its enough to use one solution and i do not know what happens
if you use both.
David
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
