Documentation Archive Developer
Search
PATH  Documentation > WebObjects 4.5 > EOControl Reference

Table of Contents

EOMessageHandlers


(informal protocol)
Declared in:
EOControl/EOEditingContext.h



Protocol Description


The EOMessageHandlers informal protocol declares methods used for error reporting and determining fetch limits. See the EOEditingContext, EODatabaseContext (EOAccess), and EODisplayGroup (EOInterface) class specifications for more information.

Message handlers are primarily used to implement exception handling in the interface layer's EODisplayGroup, and wouldn't ordinarily be used in a command line tool or WebObjects application.



Instance Methods



editingContext:presentErrorMessage:

- (void)editingContext:(EOEditingContext *)anEditingContext presentErrorMessage:(NSString *)message

Invoked by anEditingContext, this method should present message to the user in whatever way is appropriate (whether by opening an attention panel or printing the message in a terminal window, for example). This message is sent only if the method is implemented.



editingContext:shouldContinueFetchingWithCurrentObjectCount:originalLimit: objectStore:

- (BOOL)editingContext:(EOEditingContext *)anEditingContext shouldContinueFetchingWithCurrentObjectCount:(unsigned)count originalLimit:(unsigned)limit objectStore:(EOObjectStore *)objectStore

Invoked by an objectStore (such as an access layer EODatabaseContext) to allow the message handler for anEditingContext (often an interface layer EODisplayGroup) to prompt the user about whether or not to continue fetching the current result set. The count argument is the number of objects fetched so far. limit is the original limit specified an EOFetchSpecification. This message is sent only if the method is implemented.


Table of Contents