EOSharedEditingContext and ObjectsChangedInStoreNotification
EOSharedEditingContext and ObjectsChangedInStoreNotification
- Subject: EOSharedEditingContext and ObjectsChangedInStoreNotification
- From: Hunter Hillegas <email@hidden>
- Date: Mon, 13 Sep 2004 10:34:27 -0700
Hello,
According to the docs for EOSharedEditingContext, it will listen for
notifications of the type ObjectsChangedInStoreNotification.
I am using Dov's JMS change notification framework posted at WOCode.com
- it is based on the code from Wonder with some important changes.
Anyway, the JMS messages are flowing and being processed. When changes
are made in one app, the other app receives the JMS message and calls
invalidateObjectsWithGlobalIDs.
The thing is, the contents of the EOSharedEditingContext don't appear
to change.
Subsequent calls to objectsByEntityNameAndFetchSpecificationName() seem
to return the unchanged/original data.
I was under the impression that invalidateObjectsWithGlobalIDs would
send a ObjectsChangedInStoreNotification and the Shared EC would do as
the docs state:
"The shared context removes from its objectsByEntityName and
objectsByEntityNameAndFetchSpecificationName dictionaries any objects
that have been deleted, and it refaults any objects that have been
updated."
I don't see any evidence of a refault (output is the original values).
So... Any ideas on how to troubleshoot this?
Is there a way to watch/print out ObjectsChangedInStoreNotifications as
they are dispatched? Is there a way to watch when the shared EC
invalidates/refaults some of its contents?
Am I mistaken about how this should work?
Thanks,
Hunter
_______________________________________________
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