Documentation Archive Developer
Search
PATH  Documentation > WebObjects 4.5 > Creating a Java Client Application: A Tutorial

   

What are EODisplayGroups and EOEditingContexts?

EODisplayGroup

EODisplayGroups transport values between an enterprise object and a user interface object. You also need an EODatabaseDataSource, which acts on behalf of the EODisplayGroup to fetch enterprise objects from the database. In combination, EODisplayGroup and EODatabaseDataSource coordinate the flow of data between the user interface and the database. The EODisplayGroup that's created when you drag an entity from EOModeler into Interface Builder is actually a compound object that consists of both an EODisplayGroup and an EODatabaseDataSource.

EOEditingContext

When you drag an entity into the nib file window from your model, an EOEditingContext object is added to your application along with the EODisplayGroup that's created from the entity. An EOEditingContext manages the graph of enterprise objects in your application. The EOEditingContext is responsible for ensuring that all parts of your application stay in sync. When an enterprise object changes, the EOEditingContext broadcasts a notification so that other parts of the application (such as the user interface) can update themselves accordingly. The EOEditingContext also manages undo, and is the object through which you save changes to the database. For more information, see the EOEditingContext class specification in the Enterprise Objects Framework Reference.


© 1999 Apple Computer, Inc. – (Last Updated 13 Sep 99)