Re: awake() called twice on page refresh
Re: awake() called twice on page refresh
- Subject: Re: awake() called twice on page refresh
- From: Guido Neitzer <email@hidden>
- Date: Thu, 30 Oct 2008 16:42:48 -0600
On 30.10.2008, at 14:41, Chuck Hill wrote:
we're observing some behaviour we can't seem to explain. We had a
problem with
application deadlocking. It turned out that the lock was ERDPage (a
ProjectWonder
component) which locks an editing context in awake() and unlocks it
again in sleep().
That sounds odd to find this in Wonder. This is a known unsafe way
to lock editing contexts. IIRC, this was one of the reasons that
the ERXEC technology was created - safe locking with D2W. Is this
some old component that never got updated?
No, it's actually on ERD2WPage (there is no ERDPage) - not sure why it
is still in there as the editing contexts should lock automatically
with ERXEC.
From what I can see, the manual locking code can be removed as long
as the automatic locking / unlocking is used. But Anjo will know more
about that.
cug
_______________________________________________
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