Re: When (not) to use session().defaultEditingContext()
Re: When (not) to use session().defaultEditingContext()
- Subject: Re: When (not) to use session().defaultEditingContext()
- From: Mark Morris <email@hidden>
- Date: Fri, 29 Oct 2004 09:29:12 -0500
To provide another point of view, I use defaultEditingContext almost
exclusively, except when I need a peer ec (for logging activity, for
example) or when I need a child ec (finer control of sub-transactions).
I *like* the fact that it caches per session, for performance
purposes.
However, I have some navigations components to address the problem of
unsaved changes hanging around. My pages conform to a
"PageNavigationInterface", and my tab and menu components check to see
if it's okay to complete the change from one page to another. The
default is to always revert() the defaultEditingContext and change
pages, on the assumption that clicking a menu item without saving means
the user wants to abort any changes. This can be overridden for cases
where transactions span pages, etc. Also, a common scenario has the
page NOT changing, and a message displayed to the user saying something
like "This page has unsaved changes. Please save or cancel to proceed."
Regards,
Mark
_______________________________________________
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