Save This Page
Home » spring-framework-2.5.6-with-dependencies » org.springframework » orm » jpa » [javadoc | source]
org.springframework.orm.jpa
public class: JpaTemplate [javadoc | source]
java.lang.Object
   org.springframework.orm.jpa.EntityManagerFactoryAccessor
      org.springframework.orm.jpa.JpaAccessor
         org.springframework.orm.jpa.JpaTemplate

All Implemented Interfaces:
    JpaOperations, InitializingBean

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 org.springframework.dao.annotation.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 org.springframework.jndi.JndiObjectFactoryBean .

Fields inherited from org.springframework.orm.jpa.EntityManagerFactoryAccessor:
logger
Constructor:
 public JpaTemplate() 
 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
Method from org.springframework.orm.jpa.JpaTemplate Summary:
contains,   createEntityManagerProxy,   execute,   execute,   executeFind,   find,   find,   find,   findByNamedParams,   findByNamedQuery,   findByNamedQuery,   findByNamedQueryAndNamedParams,   flush,   getReference,   isExposeNativeEntityManager,   merge,   persist,   refresh,   remove,   setExposeNativeEntityManager
Methods from org.springframework.orm.jpa.JpaAccessor:
afterPropertiesSet,   flushIfNecessary,   getEntityManager,   getJpaDialect,   isFlushEager,   setEntityManager,   setFlushEager,   setJpaDialect,   translateIfNecessary
Methods from org.springframework.orm.jpa.EntityManagerFactoryAccessor:
createEntityManager,   getEntityManagerFactory,   getJpaPropertyMap,   getTransactionalEntityManager,   setEntityManagerFactory,   setJpaProperties,   setJpaPropertyMap
Methods from java.lang.Object:
equals,   getClass,   hashCode,   notify,   notifyAll,   toString,   wait,   wait,   wait
Method from org.springframework.orm.jpa.JpaTemplate Detail:
 public boolean contains(Object entity) throws DataAccessException 
 protected EntityManager createEntityManagerProxy(EntityManager em) 
    Create a close-suppressing proxy for the given JPA EntityManager. The proxy also prepares returned JPA Query objects.
 public Object execute(JpaCallback action) throws DataAccessException 
 public Object execute(JpaCallback action,
    boolean exposeNativeEntityManager) throws DataAccessException 
    Execute the action specified by the given action object within a EntityManager.
 public List executeFind(JpaCallback action) throws DataAccessException 
 public List find(String queryString) throws DataAccessException 
 public T find(Class entityClass,
    Object id) throws DataAccessException 
 public List find(String queryString,
    Object values) throws DataAccessException 
 public List findByNamedParams(String queryString,
    Map params) throws DataAccessException 
 public List findByNamedQuery(String queryName) throws DataAccessException 
 public List findByNamedQuery(String queryName,
    Object values) throws DataAccessException 
 public List findByNamedQueryAndNamedParams(String queryName,
    Map params) throws DataAccessException 
 public  void flush() throws DataAccessException 
 public T getReference(Class entityClass,
    Object id) throws DataAccessException 
 public boolean isExposeNativeEntityManager() 
    Return whether to expose the native JPA EntityManager to JpaCallback code, or rather an EntityManager proxy.
 public T merge(T entity) throws DataAccessException 
 public  void persist(Object entity) throws DataAccessException 
 public  void refresh(Object entity) throws DataAccessException 
 public  void remove(Object entity) throws DataAccessException 
 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".