Table of Contents Previous Section
New Convenience API
Enterprise Objects Framework 3.0 introduces new API to facilitate common programming tasks. Tasks that used to take several lines of code now only take one. The following sections describe the new convenience API.
EOUtilities
Most of the new convenience API is implemented in EOUtilities. In Objective-C, EOUtilities is a category on EOEditingContext provided in EOAccess. In Java, it's a new class called EOUtilities in EOAccess. The Objective-C and Java methods work the same way, but you invoke them differently. For example, compare the invocations for the following method:Objective-C
[editingContext objectsForEntityNamed:entityName];Java
EOUtilities.objectsForEntityNamed(editingContext, entityName);Both versions of the method require an editing context into which the objects should be fetched. In Objective-C, the editing context is the receiver of the message. In Java, the editing context must be passed as an argument.
Note: The Objective-C source code for EOUtilities is available as an example. On Rhapsody systems, see /System/Developer/Examples/EnterpriseObjects/Sources/EOUtilities. On NT, see NEXT_ROOT/Developer/Examples/EnterpriseObjects/Sources/EOUtilities.
The complete documentation for the Objective-C EOUtilities methods are documented in the "EOEditingContext Additions" class specification (EOAccess). The corresponding Java EOUtilities API documentation is available in the EOUtilities class specification (EOAccess). The following tables summarize the EOUtilities methods.
Note: All the Java EOUtilities methods are static methods.
Supporting Convenience Methods
The following tables describe the remainder of the convenience API.
EOModelGroup | |
---|---|
storedProcedureNamed: | Returns the stored procedure identified by the provided name. |
Table of Contents Next Section