java.lang.Object | |||
↳ | org.springframework.orm.jpa.EntityManagerFactoryAccessor | ||
↳ | org.springframework.orm.jpa.JpaAccessor | ||
↳ | org.springframework.orm.jpa.JpaTemplate |
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
.
[Expand]
Inherited Fields | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
From class
org.springframework.orm.jpa.EntityManagerFactoryAccessor
|
Public Constructors | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Create a new JpaTemplate instance.
| |||||||||||
Create a new JpaTemplate instance.
| |||||||||||
Create a new JpaTemplate instance.
|
Public Methods | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Execute the action specified by the given action object within a
EntityManager.
| |||||||||||
Return whether to expose the native JPA EntityManager to JpaCallback
code, or rather an EntityManager proxy.
| |||||||||||
Prepare the given JPA query object.
| |||||||||||
Set whether to expose the native JPA EntityManager to JpaCallback
code.
|
Protected Methods | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
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
|
Create a new JpaTemplate instance.
Create a new JpaTemplate instance.
emf | EntityManagerFactory to create EntityManagers |
---|
Create a new JpaTemplate instance.
em | EntityManager to use |
---|
Execute the action specified by the given action object within a EntityManager.
action | callback object that specifies the JPA action |
---|---|
exposeNativeEntityManager | whether to expose the native JPA entity manager to callback code |
null
DataAccessException | in case of JPA errors |
---|
DataAccessException |
---|
DataAccessException |
---|
Return whether to expose the native JPA EntityManager to JpaCallback code, or rather an EntityManager proxy.
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.
query | the JPA query object |
---|
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".
JpaCallback
Create a close-suppressing proxy for the given JPA EntityManager. The proxy also prepares returned JPA Query objects.
em | the JPA EntityManager to create a proxy for |
---|