Re: Child Editing Contexts -- locking/unlocking
Re: Child Editing Contexts -- locking/unlocking
- Subject: Re: Child Editing Contexts -- locking/unlocking
- From: David LeBer <email@hidden>
- Date: Thu, 4 Aug 2005 11:59:56 -0400
On 4-Aug-05, at 11:47 AM, Dana Kashubeck wrote:
I'm sorry if this is noise, but I've never worked with anything but
the defaultEditingContext before and I want to make absolutely sure
that I'm doing The Right Thing here.
I'm working on a wizard-like interface that resides in a
framework. The user may be creating several new EO's that they
decide at the end they don't want. Therefore, I don't want to put
them in the defaultEditingContext when they are created because I
don't want any changes to make their way there and get saved
accidentally on some other page (all of our WO apps use
defaultEditingContext exclusively). I figured this is a perfect
place for a child editing context.
The first page will create the child editing context
(defaultEditingContext is it's parent), fault in some needed
objects from the defaultEditingContext, and put it into a userInfo
dictionary in the Session. Each subsequent page will grab the
child editing context from the session in it's init method.
Now, as long as I don't perform any sort of fetches or changes on
EOs, etc. in the init method, I can simply lock the child editing
context in each component's awake method and then unlock it in the
corresponding sleep method, right? Also, I have to lock the newly
created child editing context before faulting in the objects from
it's parent, and then unlock it afterward, correct? Thanks in
advance for your help!
In general you are better to lock EC's in the session (if you've got
one) rather than the component.
As that is the usual approach, there are a couple of solutions to
implement that for you:
MultiECLockManager: <http://wocode.com/cgi-bin/WebObjects/WOCode.woa/
1/wa/ShareCodeItem?itemId=301>
Project Wonder's ERXEC: <http://wonder.sourceforge.net/javadoc/er/
extensions/ERXEC.html>
--
;david
--
David LeBer
Codebase Software Systems
site: http://www.codebase.ca
blog: http://david.codebase.ca
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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