public class

JpaTemplate

extends JpaAccessor
implements JpaOperations
java.lang.Object
   ↳ org.springframework.orm.jpa.EntityManagerFactoryAccessor
     ↳ org.springframework.orm.jpa.JpaAccessor
       ↳ org.springframework.orm.jpa.JpaTemplate

Class Overview

Helper class that allows for writing JPA data access code in the same style as with Spring's well-known JdoTemplate and HibernateTemplate classes. Automatically converts PersistenceExceptions into Spring DataAccessExceptions, following the org.springframework.dao exception hierarchy.

The central method is of this template is "execute", supporting JPA access code implementing the JpaCallback interface. It provides JPA EntityManager handling such that neither the JpaCallback implementation nor the calling code needs to explicitly care about retrieving/closing EntityManagers, or handling JPA lifecycle exceptions.

Can be used within a service implementation via direct instantiation with a EntityManagerFactory reference, or get prepared in an application context and given to services as bean reference. Note: The EntityManagerFactory should always be configured as bean in the application context, in the first case given to the service directly, in the second case to the prepared template.

NOTE: JpaTemplate mainly exists as a sibling of JdoTemplate and HibernateTemplate, offering the same style for people used to it. For newly started projects, consider adopting the standard JPA style of coding data access objects instead, based on a "shared EntityManager" reference injected via a Spring bean definition or the JPA PersistenceContext annotation. (Using Spring's SharedEntityManagerBean / PersistenceAnnotationBeanPostProcessor, or using a direct JNDI lookup for an EntityManager on a Java EE 5 server.)

JpaTemplate can be considered as direct alternative to working with the native JPA EntityManager API (through a shared EntityManager reference, as outlined above). The major advantage is its automatic conversion to DataAccessExceptions; the major disadvantage is that it introduces another thin layer on top of the native JPA API. Note that exception translation can also be achieved through AOP advice; check out PersistenceExceptionTranslationPostProcessor.

LocalContainerEntityManagerFactoryBean is the preferred way of obtaining a reference to an EntityManagerFactory, at least outside of a full Java EE 5 environment. The Spring application context will manage its lifecycle, initializing and shutting down the factory as part of the application. Within a Java EE 5 environment, you will typically work with a server-managed EntityManagerFactory that is exposed via JNDI, obtained through Spring's JndiObjectFactoryBean.

Summary

[Expand]
Inherited Fields
From class org.springframework.orm.jpa.EntityManagerFactoryAccessor
Public Constructors
JpaTemplate()
Create a new JpaTemplate instance.
JpaTemplate(EntityManagerFactory emf)
Create a new JpaTemplate instance.
JpaTemplate(EntityManager em)
Create a new JpaTemplate instance.
Public Methods
boolean contains(Object entity)
<T> T execute(JpaCallback<T> action)
<T> T execute(JpaCallback<T> action, boolean exposeNativeEntityManager)
Execute the action specified by the given action object within a EntityManager.
List executeFind(JpaCallback<?> action)
<T> T find(Class<T> entityClass, Object id)
List find(String queryString, Object... values)
List find(String queryString)
List findByNamedParams(String queryString, Map<String, ?> params)
List findByNamedQuery(String queryName, Object... values)
List findByNamedQuery(String queryName)
List findByNamedQueryAndNamedParams(String queryName, Map<String, ?> params)
void flush()
<T> T getReference(Class<T> entityClass, Object id)
boolean isExposeNativeEntityManager()
Return whether to expose the native JPA EntityManager to JpaCallback code, or rather an EntityManager proxy.
<T> T merge(T entity)
void persist(Object entity)
void prepareQuery(Query query)
Prepare the given JPA query object.
void refresh(Object entity)
void remove(Object entity)
void setExposeNativeEntityManager(boolean exposeNativeEntityManager)
Set whether to expose the native JPA EntityManager to JpaCallback code.
Protected Methods
EntityManager createEntityManagerProxy(EntityManager em)
Create a close-suppressing proxy for the given JPA EntityManager.
[Expand]
Inherited Methods
From class org.springframework.orm.jpa.JpaAccessor
From class org.springframework.orm.jpa.EntityManagerFactoryAccessor
From class java.lang.Object
From interface org.springframework.beans.factory.InitializingBean
From interface org.springframework.orm.jpa.JpaOperations

Public Constructors

public JpaTemplate ()

Create a new JpaTemplate instance.

public JpaTemplate (EntityManagerFactory emf)

Create a new JpaTemplate instance.

Parameters
emf EntityManagerFactory to create EntityManagers

public JpaTemplate (EntityManager em)

Create a new JpaTemplate instance.

Parameters
em EntityManager to use

Public Methods

public boolean contains (Object entity)

public T execute (JpaCallback<T> action)

public T execute (JpaCallback<T> action, boolean exposeNativeEntityManager)

Execute the action specified by the given action object within a EntityManager.

Parameters
action callback object that specifies the JPA action
exposeNativeEntityManager whether to expose the native JPA entity manager to callback code
Returns
  • a result object returned by the action, or null
Throws
DataAccessException in case of JPA errors

public List executeFind (JpaCallback<?> action)

public T find (Class<T> entityClass, Object id)

public List find (String queryString, Object... values)

public List find (String queryString)

public List findByNamedParams (String queryString, Map<String, ?> params)

public List findByNamedQuery (String queryName, Object... values)

public List findByNamedQuery (String queryName)

public List findByNamedQueryAndNamedParams (String queryName, Map<String, ?> params)

public void flush ()

public T getReference (Class<T> entityClass, Object id)

public boolean isExposeNativeEntityManager ()

Return whether to expose the native JPA EntityManager to JpaCallback code, or rather an EntityManager proxy.

public T merge (T entity)

public void persist (Object entity)

public void prepareQuery (Query query)

Prepare the given JPA query object. To be used within a JpaCallback.

Applies a transaction timeout, if any. If you don't use such timeouts, the call is a no-op.

In general, prefer a proxied EntityManager instead, which will automatically apply the transaction timeout (through the use of a special EntityManager proxy). You need to set the "exposeNativeEntityManager" property to "false" to activate this. Note that you won't be able to cast to a provider-specific JPA EntityManager class anymore then.

Parameters
query the JPA query object

public void refresh (Object entity)

public void remove (Object entity)

public void setExposeNativeEntityManager (boolean exposeNativeEntityManager)

Set whether to expose the native JPA EntityManager to JpaCallback code. Default is "false": a EntityManager proxy will be returned, suppressing close calls and automatically applying transaction timeouts (if any).

As there is often a need to cast to a provider-specific EntityManager class in DAOs that use the JPA 1.0 API, for JPA 2.0 previews and other provider-specific functionality, the exposed proxy implements all interfaces implemented by the original EntityManager. If this is not sufficient, turn this flag to "true".

See Also

Protected Methods

protected EntityManager createEntityManagerProxy (EntityManager em)

Create a close-suppressing proxy for the given JPA EntityManager. The proxy also prepares returned JPA Query objects.

Parameters
em the JPA EntityManager to create a proxy for
Returns
  • the EntityManager proxy, implementing all interfaces implemented by the passed-in EntityManager object (that is, also implementing all provider-specific extension interfaces)
See Also
  • javax.persistence.EntityManager#close