Direct Action needs Application's EOSharedEditingContext
Direct Action needs Application's EOSharedEditingContext
- Subject: Direct Action needs Application's EOSharedEditingContext
- From: Baiss Eric Magnusson <email@hidden>
- Date: Mon, 14 May 2007 14:10:26 -0700
In re-designing a WO app I have worked on for a year the customer
wants the "top level navigation" to go to about 60 different
WOComponents from Direct Action calls, which are invoked by WOPopup's
calling <onChange "submit();">, with the additional binding <?menuID
menuEO.primaryKeyId>, thus passing a Primary Key ID to the DA.
In the Application class I have an <EOSharedEditingContext> with all
the different records (menuEO's) describing the nature of the
WOComponent pages.
But from the <WODirectAction> sub-class I don't see a way to get to
those EO's in the <EOSharedEditingContext>. BTW: there may or may not
be a <Session> present but I have taken care of that in the DA methods.
It seems wasteful to create an EOEditingContext and do a fetch every
time a DA call is made.
I suppose a could do all the fetching in the <DirectAction>
Constructor and save it in a class global.
Any thoughts?
Thanks to all,
----
Baiss Eric Magnusson
<http://www.Track-Your-Finances.com>
<http://www.CascadeWebDesign.com>
_______________________________________________
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