Re: Child Editing Contexts -- locking/unlocking
Re: Child Editing Contexts -- locking/unlocking
- Subject: Re: Child Editing Contexts -- locking/unlocking
- From: Chuck Hill <email@hidden>
- Date: Thu, 4 Aug 2005 09:22:45 -0700
On Aug 4, 2005, at 9:17 AM, Dana Kashubeck wrote:
Chuck Hill wrote:
Some additions to David's comments:
On Aug 4, 2005, at 8:59 AM, David LeBer wrote:
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).
Perhaps not the best plan WRT memory usage / session size.
I was a bit concerned about that . . . planned to see what sort of
memory footprint I run into.
I figured this is a perfect place for a child editing context.
I'd be looking more at a peer EC, possibly with a child EC for each
page of the wizard if you need to revert just what is on that page
without affecting the changes made on other pages.
Can I still fault in objects from the defaultEditingContext?
Yes. As long as the object has been saved (that is, not a newly
inserted unsaved object or an object that has just been deleted and
saved) you can fault between _any_ two editing contexts.
The reason I ask is that the WOSession subclass that we use has
several methods that grab information from the database using the
defaultEditingContext. I'd really like to not rewrite that subclass.
I would need to fault into the peer editing context some objects that
I've obtained from the session. Can I do this or should I just do my
own fetch and not use the session's methods?
You won't need any code changes.
Chuck
--
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