Jump to: navigation, search

Difference between revisions of "EclipseLink/UserGuide/JPA/Basic JPA Development/Entities/Creating and Configuring Entities"

(Configuring an Entity's Table)
(Configuring Inheritance)
Line 72: Line 72:
 
*[[EclipseLink/UserGuide/JPA/Basic JPA Development/Entities/Inheritance|@Inheritance]]  
 
*[[EclipseLink/UserGuide/JPA/Basic JPA Development/Entities/Inheritance|@Inheritance]]  
 
*[[EclipseLink/UserGuide/JPA/Basic JPA Development/Entities/MappedSuperclass|@MappedSuperclass]]  
 
*[[EclipseLink/UserGuide/JPA/Basic JPA Development/Entities/MappedSuperclass|@MappedSuperclass]]  
*[[EclipseLink/UserGuide/JPA/Basic JPA Development/Entities/Inheritance#Advanced Inheritance|Advanced Inheritance Configuration]]  
+
*[[EclipseLink/UserGuide/JPA/Basic JPA Development/Entities/Inheritance#Advanced Inheritance Configuration|Advanced Inheritance Configuration]]  
  
 
<br>  
 
<br>  

Revision as of 12:39, 29 June 2011

EclipseLink JPA

Configuring Entities

An entity is a lightweight persistence domain object. Typically, an entity represents a table in a relational database, and each entity instance corresponds to a row in the table. The primary programming artifact of an entity is the entity class, although entities can use helper classes.

The persistent state of an entity is represented either through persistent fields or persistent properties. These fields or properties use object/relational mapping annotations to map the entities and entity relationships to the relational data in the underlying data store.

Identifying an Entity

Use the @Entity annotation to specify that a class is an entity, as shown in the following example:

@Entity
public class Employee implements Serializable {
...
}

Elug note icon.png

Note: The entity class must also be listed in your persistence.xml file, unless you set the tag <exclude-unlisted-classes> to false. An entity can also be defined using an orm.xml file and the <entity> tag.

Elug javaspec icon.gif

For more information, see Chapter 2 "Entities" in the JPA Specification.

Configuring an Entity's Persistent Identity

Every entity must have a persistent identity, which is an equivalent of a primary key in a database table that stores the entity state.

By default, the EclipseLink persistence provider assumes that each entity has at least one field or property that serves as a primary key.

You can generate and/or configure the identity of your entities by using the following annotations:

You can also use these annotations to fine-tune how your database maintains the identity of your entities.

Elug note icon.png

Note: If your class does not have a logical Id then you need to add a generated one. Embedded objects do not require an Id.


Configuring an Entity's Table

Every entity class maps to a specific table or set of tables in the database. By default the entity's table name is defaulted as its entity name as uppercase, which defaults to the entity's short class name. An entity normally maps to a single table, but can also map to multiple tables, or even a view.

You can customize an entity's tables using the following annotations:

For information on how to create the tables in the database see, Schema Generation.

Configuring Inheritance

JPA defines several difference methods for persisting objects with inheritance. The @Inheritance annotation is used in the root class to define SINGLE_TABLE, JOINED, and TABLE_PER_CLASS inheritance. For abstract classes that define common state or persistence behavior, but have no relationship on the database, the @MappedSuperclass annotation can be used.



Eclipselink-logo.gif
Version: 2.2.0 DRAFT
Other versions...