Re: A WOLongResponsePage that _sometimes_ seems to create a deadlock
Re: A WOLongResponsePage that _sometimes_ seems to create a deadlock
- Subject: Re: A WOLongResponsePage that _sometimes_ seems to create a deadlock
- From: Chuck Hill <email@hidden>
- Date: Mon, 9 May 2005 09:37:32 -0700
I'll repeat Anjo's warning because it is well worth repeating. :-)
IIRC, Apple's D2W pages are notoriously bad for doing this. At the
very, very least you are going to need an isLocked flag to avoid over
locking or over unlocking. But it is best to use ERXEC or the
MultiECLockManager which handle this in an altogether safer way.
Chuck
On May 6, 2005, at 9:03 AM, Anjo Krank wrote:
Am 06.05.2005 um 16:56 schrieb Kaj Hejer:
public void awake() {
super.awake();
if (editingContext != null && isPerformActionFinished) {
editingContext.lock(); //line 103
}
}
Never, *EVER* lock ECs in awake and sleep without some safety measure
like ERXEC or this other thing of which I cant remember the name. You
are not in the least guaranteed that the calls balance!
--
Practical WebObjects - a book for intermediate WebObjects developers
who want to increase their overall knowledge of WebObjects, or those
who are trying to solve specific application development problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
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