跳至主要内容

Use native JPA API

Use native JPA API

Since Spring 3.0, Spring embrace JPA quickly, and JPA is the first class citizen in Spring core framework. And in the latest Spring, JPA support is improved and the usage of JPA is more friendly than Hibernate.

Configuration

An example of XML format configuration is shown below:
<jdbc:embedded-database id="dataSource" >    
</jdbc:embedded-database>

<bean class="org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean"
id="entityManagerFactory">
    <property name="persistenceUnitName" value="persistenceUnit" />
    <property name="dataSource" ref="dataSource" />
    <property name="persistenceProviderClass" value="org.hibernate.ejb.HibernatePersistence"></property>
    <property name="packagesToScan">
        <array>
            <value>com.hantsylabs.example.spring.model</value>
        </array>
    </property>
    <property name="jpaProperties">
        <value>
            hibernate.format_sql=true
            hibernate.show_sql=true
            hibernate.hbm2ddl.auto=create
        </value>
    </property>
</bean>

<bean class="org.springframework.orm.jpa.JpaTransactionManager"
        id="transactionManager">
    <property name="entityManagerFactory" ref="entityManagerFactory" />
</bean>

<context:component-scan
 base-package="com.hantsylabs.example.spring.dao,com.hantsylabs.example.spring.jpa">
</context:component-scan>
Firstly, it declares a DataSource bean.
Then registers a EntityManagerFactoryBean bean, there are two version of EntityManagerFactoryBean are provided in Spring.
  • LocalEntityManagerFactoryBean reads the standard JPA configuration file from /META-INF/peresistence.xml in the project and prepare a JPA EntityManagerFactory at runtime.
  • LocalContainerEntityManagerFactoryBean is an advanced version and it provides more features. It is more friendly for container environment. It allow you specify the location of persistence.xml file. You can also configure a Spring loadTimeWeaver. Use this version, you can reuse the DataSource bean, and override the properties. In another word, you are free from maintaining the JPA specific configuration file( /META-INF/persistence.xml), you do not need it at all.
In this example, LocalContainerEntityManagerFactoryBean is used, and no JPA specific configuration file( /META-INF/persistence.xml) is placed in projects, the LocalContainerEntityManagerFactoryBean bean is responsible for building the JPA resources for you.
At last declare a JPA transaction manager.
The following is the Java configuration example, it is equivalent to the before XML format.
@Configuration
@ComponentScan(basePackages = { "com.hantsylabs.example.spring.dao",
        "com.hantsylabs.example.spring.jpa" })
public class JpaConfig {

    @Bean
    public DataSource dataSource() {
        return new EmbeddedDatabaseBuilder().build();
    }

    @Bean
    public LocalContainerEntityManagerFactoryBean entityManagerFactory() {
        LocalContainerEntityManagerFactoryBean emf = new LocalContainerEntityManagerFactoryBean();
        emf.setDataSource(dataSource());
        emf.setPackagesToScan("com.hantsylabs.example.spring.model");
        emf.setPersistenceProvider(new HibernatePersistence());
        emf.setJpaProperties(jpaProperties());
        return emf;
    }

    private Properties jpaProperties() {
        Properties extraProperties = new Properties();
        extraProperties.put("hibernate.format_sql", "true");
        extraProperties.put("hibernate.show_sql", "true");
        extraProperties.put("hibernate.hbm2ddl.auto", "create");
        return extraProperties;
    }

    @Bean
    public PlatformTransactionManager transactionManager() {
        return new JpaTransactionManager(entityManagerFactory().getObject());
    }

}

Example codes

@Repository
public class JpaConferenceDaoImpl implements ConferenceDao {
    private static final Logger log = LoggerFactory
            .getLogger(JpaConferenceDaoImpl.class);

    @PersistenceContext
    private EntityManager entityManager;

    @Override
    public Conference findById(Long id) {
        return (Conference) entityManager.find(Conference.class, id);

    }
}
As you see, it uses @PersistenceContext to inject the JPA EntityManager bean, there is only one Spring specific @Repository annotation in the above codes.
If you are using JSR330, you can replace the @Repository with @Named, we will discuss this topic in further posts.
@Named
public class JpaConferenceDaoImpl implements ConferenceDao {

    @PersistenceContext
    private EntityManager entityManager;

}
Now, the above codes are no difference between Spring and Java EE, it can be run in Spring(especially a Servlet container, such as Apache Tomcat, Jetty) and any standard Java EE 6 container(for example JBoss AS 7, Glassfish 3.1). Of course you have to contribute extra effort on the base configuration for different platform.

Check out the codes from my github.com,  https://github.com/hantsy/spring-sandbox.

评论

此博客中的热门博文

AngularJS CakePHP Sample codes

Introduction This sample is a Blog application which has the same features with the official CakePHP Blog tutorial, the difference is AngularJS was used as frontend solution, and CakePHP was only use for building backend RESR API. Technologies AngularJS   is a popular JS framework in these days, brought by Google. In this example application, AngularJS and Bootstrap are used to implement the frontend pages. CakePHP   is one of the most popular PHP frameworks in the world. CakePHP is used as the backend REST API producer. MySQL   is used as the database in this sample application. A PHP runtime environment is also required, I was using   WAMP   under Windows system. Post links I assume you have some experience of PHP and CakePHP before, and know well about Apache server. Else you could read the official PHP introduction( php.net ) and browse the official CakePHP Blog tutorial to have basic knowledge about CakePHP. In these posts, I tried to follow the steps describ

JPA 2.1: Attribute Converter

JPA 2.1: Attribute Converter If you are using Hibernate, and want a customized type is supported in your Entity class, you could have to write a custom Hibernate Type. JPA 2.1 brings a new feature named attribute converter, which can help you convert your custom class type to JPA supported type. Create an Entity Reuse the   Post   entity class as example. @Entity @Table(name="POSTS") public class Post implements Serializable { private static final long serialVersionUID = 1L; @Id @GeneratedValue(strategy = GenerationType.AUTO) @Column(name="ID") private Long id; @Column(name="TITLE") private String title; @Column(name="BODY") private String body; @Temporal(javax.persistence.TemporalType.DATE) @Column(name="CREATED") private Date created; @Column(name="TAGS") private List<String> tags=new ArrayList<>(); } Create an attribute convert

Auditing with Hibernate Envers

Auditing with Hibernate Envers The approaches provided in JPA lifecyle hook and Spring Data auditing only track the creation and last modification info of an Entity, but all the modification history are not tracked. Hibernate Envers fills the blank table. Since Hibernate 3.5, Envers is part of Hibernate core project. Configuration Configure Hibernate Envers in your project is very simple, just need to add   hibernate-envers   as project dependency. <dependency> <groupId>org.hibernate</groupId> <artifactId>hibernate-envers</artifactId> </dependency> Done. No need extra Event listeners configuration as the early version. Basic Usage Hibernate Envers provides a simple   @Audited   annotation, you can place it on an Entity class or property of an Entity. @Audited private String description; If   @Audited   annotation is placed on a property, this property can be tracked. @Entity @Audited public class Signup implements Serializa