Re: To Many Fault and Locking
Re: To Many Fault and Locking
- Subject: Re: To Many Fault and Locking
- From: email@hidden
- Date: Tue, 18 May 2004 08:43:27 +0100
Hunter,
This component is setup by a direct action. There is no session. I was
under the impression that to use the MultiECLockManager I need to be
using session derived ECs. Maybe I should look at the code again.
<snip>
So, I guess I'm not sure how to lock the EO since the exception is
being generated while in my Java code, but from the component
template.
You have two solutions to that. You can follow the same pattern as the
default editing context, which is locked on awake() and unlocked on
sleep().
The other solution is to look at which time the editing context is
used. The component bindings are resolved in appendToResponse, so you
can lock the editing context before calling super.
Does that make more sense?
Hope this helps,
-- Denis.
On May 16, 2004, at 10:16 PM, Chuck Hill wrote:
The best thing is to keep the EC locked. You should not do anything
to any
eo in an ec unless the ec is locked. See the MultiECLockManager on
WOCode
for a good solution to this.
Chuck
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.