• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Invalidating EOSharedEditingContext through DirectAction
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Invalidating EOSharedEditingContext through DirectAction


  • Subject: Re: Invalidating EOSharedEditingContext through DirectAction
  • From: Dev WO <email@hidden>
  • Date: Fri, 29 Sep 2006 20:31:26 +0200

Hi Chuck:)


On Sep 29, 2006, at 10:26 AM, Dev WO wrote:

Hi,
I've been trying to force a refresh of a sharedEC using Direct Action, but I just can't find a way to access the application's SharedEC through my DirectAction class.
I tried:



Yes, blank lines are unlikely to work. ;-)
aaaaah I can't believe I didn't paste anything... What I got was wrong, but not blank:)

How about this:

EOSharedEditingContext sharedEC = EOSharedEditingContext.defaultSharedEditingContextt();
At least it compiles:)
I'll try to see if it works as expected:)

Xavier


Chuck

but got an issue about static context.

So here's my situation:
-a back office application
-a front office application
-a framework

I need to "force" an update of the front office when the back office is updating/adding/removing an object.
Always the same "data-freshness vs power-consumption" thing:)


What's new today is that I now have my application (at least the front office) linked against the Wonder frameworks, so maybe I have some "other" ways than just trying to force a refresh of the entire front office sharedEC...

I can also linked the back office to Wonder if there's a nice way through it:) (not sure I have to do something specific for the framework)

I didn't find anything for now, anyone with a pointer?

Thanks a lot

Xavier

PS: There may also be a way through the use of notification or something like this, to allow the back office and front office to listen to each other, but I'm really not confident about that, so if it's the way I should go, thanks for a little more than just a pointer;)

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40global-village.net


This email sent to email@hidden


--

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@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
References: 
 >Invalidating EOSharedEditingContext through DirectAction (From: Dev WO <email@hidden>)
 >Re: Invalidating EOSharedEditingContext through DirectAction (From: Chuck Hill <email@hidden>)

  • Prev by Date: Re: Invalidating EOSharedEditingContext through DirectAction
  • Next by Date: SVN, WOBuilder/WOComponents and Eclipse
  • Previous by thread: Re: Invalidating EOSharedEditingContext through DirectAction
  • Next by thread: SVN, WOBuilder/WOComponents and Eclipse
  • Index(es):
    • Date
    • Thread