PATH WebObjects 4.0 Documentation > EOF Developer's Guide

Table of Contents

Previous Section

Enterprise Objects

So far, you've seen the components of an application that Enterprise Objects Framework provides. The component of an application that the Framework doesn't provide-the part that you write-is your application's business logic. Typically you code the bulk of this business logic in enterprise object classes.

An enterprise object is like any other object in that it couples data with the methods for operating on that data. However, an enterprise object class has certain characteristics that distinguish it from other classes:

It has properties that map to stored or persistent data; an enterprise object instance typically corresponds to a single row or record in a database.
It knows how to interact with other parts of the Framework to give and receive values for its properties.

Although you write the business logic, the Framework specifies how it gets invoked. In addition to providing classes that manage a graph of enterprise objects in memory, the control layer defines an API to which enterprise objects must conform. So you can concentrate on the parts of your enterprise object classes that are specific to your application, it also provides default implementations of most of this API.

To find out more about writing enterprise object classes, see the chapter "Designing Enterprise Objects".

Table of Contents Next Section