Do you have multiple EOF stacks? If not, just use EOSharedEditingContext.defaultSharedEditingContext()

Chuck

On May 14, 2007, at 2:10 PM, Baiss Eric Magnusson wrote:

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 protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/chill% 40global-village.net

This email sent to [EMAIL PROTECTED]


--

Practical WebObjects - for developers who want to increase their overall knowledge of WebObjects or who are trying to solve specific 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 protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to [EMAIL PROTECTED]

Reply via email to