data entity

The customizations apply to the entire Web site, not just to a single data entity, and are independent of any specific database.

With this approach each data entity includes both the attributes and the inherited attributes of the class that it represents.

You can limit the customization of a specific data entity to a single custom page.

To implement this relationship I used the attribute positionOID, the key of the Position data entity, in the Employee data entity.

The example identified the problem of selecting a clock reference for shared data entity program components to use.

This enables logical separation of the data access and data entity tiers.

Figure 7 presents the persistence model when each concrete class is mapped to a data entity.

the data layer provides the data entity for the application of models.

Figure 6 presents the updated persistence model for mapping the entire class hierarchy into one data entity.

Figure 8 presents the solution for the third mapping strategy -- mapping a single class to a single data entity.

This lets you customize the UI for a whole data entity such as a row or a table.

If you are dealing with multiple sources, then you harmonize until you have a single definition or survivable data entity to map to.

Using one data entity for an entire class hierarchy

Using one data entity per concrete class

Using one data entity per class

Data-entity processing rules, such as stored procedures