People who downloaded this DZone Refcard also liked:

Getting Started with JPA

By Mike Keith

Geting Started With JPA

The Java Persistence API (JPA) is the Java standard for mapping Java objects to a relational database. Even though proprietary mapping products like Hibernate and TopLink still exist, they are now focused on providing their functionality through the JPA API, allowing all applications to be portable across JPA implementations. This refcard will give users enough to understand the basics of JPA and get started writing JPA applications. It covers entities, identifiers, O-R mappings, using an entity manager, creating and executing queries, and configuration of the persistence.xml file.

Mapping An Object

The basic unit of persistence in JPA is the entity, which is nothing more than a regular Java class with metadata to describe how its state maps to the database tables. Metadata may be in the form of annotations on the entity class itself, or it may be an accompanying XML file, but we are using annotations since they are easier to specify and understand.

Every entity class should have an @Entity marker and an identifier field, indicated by @Id, that is mapped to the primary key column in the database. When a field contains simple data and maps to a regular column in the database we call it a basic mapping, thus an identifier field is a special kind of basic mapping. When an entity has a field that references one or more other entities, that field maps to a foreign key column, and is called a relationship field. Other than the identifier field, basic mappings do not need to be annotated, but relationships must be specified by their relationship cardinality.

Defaulting rules in JPA mean that you are not required to specify table names and column names that an entity is mapped to. If you are not happy with the JPA-assigned defaults then you can always override them through the use of additional mapping metadata. For example, by putting @Table on the entity class you can make the table name explicit, and by annotating a basic mapping field with @Column you can define the particular column that maps the state in that field. Likewise @JoinColumn is used to override the name of the foreign key column for relationship references.

An example of two mapped entities are the Pet and Owner classes shown in Listings 1 and 2.

Listing 1 - Pet entity class

@Entity
@Table(name="PET_INFO")
public class Pet {
@Id
@Column(name="ID")
int licenseNumber;
String name;
PetType type;
@ManyToOne
@JoinColumn(name="OWNER_ID")
Owner owner;
...
}

Listing 2 - Owner entity class
@Entity
public class Owner {
@Id
int id;
String name;
@Column(name="PHONE_NUM")
String phoneNumber;
@OneToOne
Address address;
@OneToMany(mappedBy="owner")
List<Pet> pets;
...
}

In a bidirectional relationship pair, such as the @OneToMany relationship in Owner to Pet and the @ManyToOne relationship back from Pet to Owner, only one foreign key is required in one of the tables to manage both sides of the relationship. As a general rule, the side that does not have the foreign key in it specifies a mappedBy attribute in the relationship annotation and specifies the field in the related entity that maps the foreign key.

The possible mapping annotations that can be used are:

@Basic      @Enumerated  @ManyToOne  @Temporal
@Embedded   @Lob         @OneToMany  @Transient
@EmbeddedId @ManyToMany  @OneToOne

@AttributeOverride(s)    @PrimaryKeyJoinColumn(s)
@AssociationOverride(s)  @SecondaryTable(s)
@Column                  @SequenceGenerator
@DiscriminatorColumn     @Table  
@JoinColumn(s)           @TableGenerator  
@JoinTable

@Entity          @IdClass             @MappedSuperclass
@Embeddable      @Inheritance         @OrderBy
@GeneratedValue  @DiscriminatorValue  @Version
@Id              @MapKey

Obtaining an Entity Manager

The EntityManager class is the main API in JPA. It is used to create new entities, manufacture queries to return sets of existing entities, merge in the state of remotely modified entities, delete entities from the database, and more.

There are, generally speaking, two main kinds of entity managers:

Listing 3 - Obtaining a non-managed entity manager

import javax.persistence.*;
...
EntityManagerFactory emf = Persistence
.createEntityManagerFactory("PetShop");
EntityManager em = emf.createEntityManager();
...
em.close();

In Listing 4 we see how a standard host container can provide a simpler way to obtain an entity manager. The only catch is that this is only supported within standard Java EE components (or containers that are compliant to the JPA container contract), so this example uses a stateless session bean.

Listing 4 - Injecting a managed entity manager

@Stateless
public class MyBean implements MyInterface {
@PersistenceContext(unitName="PetShop")
EntityManager em;
...
}

Using an Entity Manager

The basic purpose of an entity manager is to perform create/ read/update/delete (CRUD) operations on entities. Listing 5 shows methods that perform these operations.

Listing 5 - Invoking the entity manager

public Pet createPet(int idNum, String name, PetType
type) {
Pet pet = new Pet(idNum, name, type);
em.persist(pet);
return pet;
}
public Pet findPet(int id) {
return em.find(Pet.class, id);
}
public Pet changeName(int id, String newName) {
Pet pet = this.findPet(id);
pet.setName(newName);
return pet;
}
public void deletePet(int id) {
Pet pet = this.findPet(id);
em.remove(pet);
}

Note that finding the pet is the first step to being able to perform update and delete operations on it. Also, an update does not even involve invoking the entity manager, but requires reading the pet, loading it into the entity manager and then modifying it. The modification will be reflected in the database when the transaction is committed.

Transactions

Since we just mentioned transactions, but didn't explain them, now would be a good time to state that JPA supports two different kinds of transactions.

JTA transactions are started and committed using the usual container techniques, either calling the UserTransaction API or making use of container-managed transaction demarcation in EJB or Spring. For example, if the methods in Listing 5 were in a session bean that had a Required transaction attribute setting then a transaction would be started at the beginning and committed at the end of each client method invocation.

When using local transactions the transaction must be demarcated manually by invoking on the EntityTransaction instance accessed from the entity manager. Each of the three methods in Listing 5 that caused the database to change would need to have begin and commit calls, as shown in Listing 6 for the persist method. Methods that only read from the database do not need to occur within a transaction.

Listing 6 - Using EntityTransaction

type) {
em.getTransaction().begin();
Pet pet = new Pet(idNum, name, type);
em.persist(pet);
em.getTransaction().commit();
return pet;
}

The complete EntityManager API is listed in Table 1, with a brief description of what each method does.

Table 1. EntityManager method summary

Querying

Dynamic queries are objects that are created from an entity manager, and then executed. The query criteria are specified at creation time as a Java Persistence Query Language (JP QL) string. Before executing the query a number of possible configuration method calls may be made on the query instance to configure it. Listing 7 shows an example of creating and executing a query that returns all the instances of Pet, or the first 100 if there are more than 100 instances.

Listing 7 - Creating and executing a dynamic query

Query q = em.createQuery("SELECT p FROM Pet p");
q.setMaxResults(100);
List results = q.getResultList();

A named query is a query that is defined statically and then instantiated and executed at runtime. It can be defined as an annotation on the entity class, and assigned a name that is used when the query is created. Listing 8 shows a named query defined on the Pet entity.

Listing 8 - Defining a named query

@NamedQuery(name="Pet.findByName",
query="SELECT p FROM Pet p WHERE p.name LIKE :pname")
@Entity
public class Pet {
...
}

The last identifier is prefixed with a colon (:) character to indicate that it is a named parameter that must be bound at runtime before the query can be executed. Listing 9 shows a method that executes the query by first instantiating a Query object using the createNamedQuery() factory method, then binding the pname named parameter to the name that was passed into the method, and finally executing the query by invoking getResultList().

Listing 9 - Executing a named query

public List findAllPetsByName(String petName) {
Query q = em.createNamedQuery("Pet.findByName");
q.setParameter("pname", petName);
return q.getResultList();
}

The entire Query API is shown in Table 2.

Table 2. Query method summary

Java Persistence Query Language

The Java Persistence Query Language is SQL-like, but operates over the entities and their mapped persistent attributes instead of the SQL schema. Many of the SQL functions and even reserved words are supported in JP QL.

There are three basic types of JP QL statements, of which the first is monstrously the most popular and useful: selects, bulk updates and bulk deletes.

1. select_clause from_clause [where_clause] [groupby_clause]
[having_clause] [orderby_clause]
2. update_clause [where_clause]
3. delete_clause [where_clause]

A simplified table of most of the supported syntax is in Table 4. For complete and precise grammar, consult the JPA specification at http://jcp.org/aboutJava/communityprocess/final/jsr220/index.html. The primitive terms are shown in Table 3.

Table 3. Primitive terms for JP QL grammar

Table 4. Simplified JP QL Grammar

Configuration

Without counting the mappings from the entity to the database tables, there is really only one unit of JPA configuration needed to get your application up and running. It is based on the notion of a persistence unit, and is configured in a file called persistence.xml, which must always be placed in the METAINF directory of your deployment unit. Each persistence unit is a configuration closure over the settings necessary to run in the relevant environment. The parent element in a persistence.xml file is the persistence element and may contain one or more persistence-unit elements representing different execution configurations. Each one must be named using the mandatory persistence-unit name attribute.

There are slightly different requirements for configuring the persistence unit, depending upon whether you are deploying to a managed container environment or a non-managed one. In a managed container the target database is indicated through the jta-data-source element, which is the JNDI name for the managed data source describing where the entity state is stored for that configuration unit. In a non-managed environment the target database is typically specified through the use of vendor-specific properties that describe the JDBC driver and connection properties to use. Also, in non-managed environments the entity classes must be enumerated in class elements, whereas in managed containers the entity classes will be automatically detected. Examples of container and noncontainer persistence unit elements are indicated in Listings 10 and 11, respectively.

Listing 10 - Container persistence unit configuration

<persistence-unit name="PetShop">
<jta-data-source>jdbc/PetShopDB</jta-data-source>
</persistence-unit>

Listing 11 - Non-container persistence unit configuration

<persistence-unit name="PetShop">
<class>com.acme.petshop.Pet</class>
...
<class>com.acme.petshop.Owner</class>
<properties>
<property name="eclipselink.jdbc.driver"
value="oracle.jdbc.OracleDriver"/>
<property name="eclipselink.jdbc.url"
value="jdbc:oracle:thin:@localhost:1521:XE"/>
<property name="eclipselink.jdbc.user"
value="scott"/>
<property name="eclipselink.jdbc.password"
value="tiger"/>
</properties>
</persistence-unit>

A hierarchical view of the possible XML elements in a persistence.xml file are shown in Figure 1. All of the elements are optional and the starred elements may be pluralized.

Figure 1. XML elements in persistence.xml file

Moving on

As you may have noticed, using JPA is not that hard, and you win the big prizes of portability and compatibility going forward. Hopefully you are now feeling ready to cut your teeth on a JPA application of your very own. The next step is to download the open source JPA 1.0 Reference Implementation (TopLink Essentials) and start it up. It is available at https://glassfish.dev.java.net/downloads/persistence/JavaPersistence. html and is trivial to install and configure. Happy persisting!

Resources

About The Author

Mike Keith

Mike Keith was a co-lead of the EJB 3.0 and JPA 1.0 specifications and coauthored the premier JPA reference book called Pro EJB 3: Java Persistence API. He has 18 years of teaching, research and development experience in object-oriented and distributed systems, specializing in object persistence. He currently works as an architect for Java and persistence strategies at Oracle and represents Oracle on the JPA 2.0 and Java EE 6 expert groups. He has authored a host of articles and papers and is a popular speaker at numerous conferences and events around the world.

Publications

• Pro EJB 3: Java Persistence API, Mike Keith and Merrick Schincariol, Apress, May 2006
• ACM Queue, May/June 2008, Exposing the ORM Cache
• JavaLobby, June 2008, Looking Forward to JPA 2.0-Part 2
• JavaLobby, April 2008, Looking Forward to JPA 2.0-Part 1

Current projects:

• n Committer on Eclipse Persistence Project
• Member of JSR 316-Java EE 6
• Member of JSR 317-JPA 2.0
• Member of JSR 318-EJB 3.1
• Member of Java EE subcommittee of OSGi Alliance EEG

Recommended Book

Assuming a basic knowledge of Java, SQL and JDBC, this book will teach you the Java Persistence API from the ground up. After reading it, you will have an in-depth understanding of JPA and learn many tips for using it in your applications.

---

BUY NOW

books.dzone.com/books/java-persistence