re: EOSharedEditingContext
re: EOSharedEditingContext
- Subject: re: EOSharedEditingContext
- From: Jonathan Miller <email@hidden>
- Date: Thu, 20 Dec 2007 18:53:36 -1000
Hi Art,
I've received that advice before, but I've also watched a screen cast
from one of the WWDC events and the apple engineer strongly recommends
using the shared editing context. If I remember correctly, the
engineer stated that iTunes heavily utilizes the shared editing context.
However, I'll go with your suggestion and stop using the static
eoutilities methods in place of the thread safe API.
Any comments?
Jon
How do I do the following without getting the pesky warning from
Eclipse about unchecked type conversion?
NSArray<NewsKeywords> newsKeywords =
EOUtilities
.objectsForEntityNamed
(EOSharedEditingContext.defaultSharedEditingContext(),
"NewsKeywords");
I wouldn't do the above in the first place. Just because an
EOSharedEditingContext extends EOEditingContext doesn't mean that it
IS an EOEditingContext. It's actually quite different and can be the
cause of considerable grief when not handled correctly (deadlocks and
other nasty behaviors). It's probably best to fetch shared objects
only early in an app's life (e.g., in the Application constructor) or
to mark objects as shared in one's eomodel which will cause them all
to be fetched when the first shared object is fetched.
NewsKeywords should be fetched into an EOSharedEditingContext using
its thread-safe API, objectsWithFetchSpecification() or
bindObjectsWithFetchSpecification(), and these fetched objects
accessed only using the thread-safe API, objectsByEntityName() or
objectsByEntityNameAndFetchSpecificationName(). You may be able to
avoid the unchecked type conversion warnings by doing so as well.
Aloha,
Art
_______________________________________________
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