I don't remember the details of how the ChangeNotification framework
works, but if you invalidate using an EOGlobalID, your object hierarchy
shouldn't matter.

What we do instead of the ChangeNotification framework is we use
something called "spread" to allow broadcasting global IDs using
NSArchiving between our many (30?) application instances. A thread
listens to the spread broadcasts and stores them in a queue, which each
app instance sucks dry about once every 5 minutes and invalidates.

(This is all in WO 4.5).

BTW, ObjC has a certain amount of reflection. It just that the methods
haven't be collected into an API, but they're there. In EOF where you
can also query the model about the entities as well which goes beyond
Java.

Pierce