跳至主要内容

Use native Hibernate 4 API

Use native Hibernate 4 API

In Spring 3.1, a new package named org.springframework.orm.hibernate4 is included( in spring-orm maven dependency). With this new APIs, using Hibernate 4 in Spring projects becomes more easy than before, you are not required to extend the HiberanteDaoSupport class or use HibernateTemplate in your implemnetation class.
Only a simple registration is required in Spring configuration, you can use the Hibernate native Session API freely in your Spring projects.
  1. Register a DataSource bean
    <jdbc:embedded-database id="dataSource" >
    </jdbc:embedded-database>
    
  2. Declare Spring specific LocalSessionFactoryBean bean.
    <bean id="sessionFactory"
        class="org.springframework.orm.hibernate4.LocalSessionFactoryBean">
        <property name="dataSource" ref="dataSource" />
        <property name="packagesToScan">
            <list>
                <value>com.hantsylabs.example.spring.model</value>
            </list>
        </property>
        <property name="hibernateProperties">
            <value>
                hibernate.dialect=org.hibernate.dialect.HSQLDialect
                hibernate.format_sql=true
                hibernate.show_sql=true
                hibernate.hbm2ddl.auto=create
            </value>
        </property>
    </bean>
    
    The legacy Spring Hibernate3 integration provides two version of SessionFactoryBean, ~.hibernate3.LocalSessionFactoryBean targets the legacy Hibernate XML mapping configuration, ~.hibernate3.annotation.AnnotationSessionFactoryBean is use for annotation based configuration.
  3. Register a transaction manager.
    <bean id="transactionManager"
    class="org.springframework.orm.hibernate4.HibernateTransactionManager">
    <property name="sessionFactory" ref="sessionFactory" />
    </bean>
    
  4. Now you can inject SessionFactory in your implementation class freely.
    @Repository
    public class Hibernate4ConferenceDaoImpl implements ConferenceDao {
    private static final Logger log = LoggerFactory
            .getLogger(Hibernate4ConferenceDaoImpl.class);
    
    @Autowired
    SessionFactory sessionFactory;
    
    private Session session() {
        return sessionFactory.getCurrentSession();
    }
    
    @Override
    public Conference findById(Long id) {
        return (Conference) session().load(Conference.class, id);
    
    }
    
    // other methods...
    }
    
    It is very simple and stupid. All the codes are based on Hibernate Session APIs now.
    NOTE: Hibernate 3 also can be configured like these, I do not demonstrate the steps here.
For the newest project, you can also use the Spring fluent java configuration API for all Spring configurations instead of the XML configuration.
The following is an example of the Java configuration, it is equivalent to the XML format above.
@Configuration
@ComponentScan(basePackages={"com.hantsylabs.example.spring.dao","com.hantsylabs.example.spring.hibernate4"})
public class HibernateConfig {

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

    @Bean
    public SessionFactory sessionFactory() {
        LocalSessionFactoryBuilder builder = new LocalSessionFactoryBuilder(
                dataSource());
        builder.scanPackages("com.hantsylabs.example.spring.model")
                .addProperties(hibernateProperties());

        return builder.buildSessionFactory();
    }

    private Properties hibernateProperties() {
        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 HibernateTransactionManager(sessionFactory());
    }

}
The configuration class is annotated with annotation @Configuration. In this class, a DataSource bean, a SessionFactoryBean, a TransactionManager bean are defined respectively. A EmbeddedDatabaseBuilder is provided to produce a DataSource bean, a LocalSessionFactoryBuilder is designated for building a SessionFactory bean. The Builder pattern is more friendly for setting some properties.

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

评论

此博客中的热门博文

Build a Reactive application with Angular 5 and Spring Boot 2.0

I have created a post to describe Reactive programming supports in Spring 5 and its subprojects, all codes of this article are updated the latest Spring 5 RELEASE, check spring-reactive-sample under my Github account.
In this post, I will create a simple blog system, including:
A user can sign in and sign out.An authenticated user can create a post.An authenticated user can update a post.Only the user who has ADMIN role can delete a post.All users(including anonymous users) can view post list and post details.An authenticated user can add his comments to a certain post. The backend will be built with the latest Spring 5 reactive stack, including:
Spring Boot 2.0, at the moment the latest version is 2.0.0.M7Spring Data MongoDB supports reactive operations for MongoDBSpring Session adds reactive support for WebSessionSpring Security 5 aligns with Spring 5 reactive stack The frontend is an Angular based SPA and it will be generated by Angular CLI.
The source code is hosted on Github, …

Activating CDI in JSF 2.3

Activating CDI in JSF 2.3 When I upgraded my Java EE 7 sample to the newest Java EE 8, the first thing confused me is the CDI beans are not recoganized in Facelects template in a JSF 2.3 based web applicaiton, which is working in the development version, but in the final release version, they are always resolved as null. I filed an issue on Mojarra and discussed it with the developers from communities and the JSF experts.
According to the content of README, In a JSF 2.3 application, to activate CDI support, declaring a 2.3 versioned faces-config.xml and adding javax.faces.ENABLE_CDI_RESOLVER_CHAIN in web.xml is not enough, you have to declare @FacesConfig annotated class to enable CDI.
Here is the steps I created a workable JSF 2.3 applicatoin in Java EE 8.
Create a Java web application, this can be done easily by NetBeans IDE, or generated by Maven archetype, for exmaple.
$ mvn archetype:generate -DgroupId=com.example -DartifactId=demo -DarchetypeArtifactId=maven-archetype-we…

JSF 2.3:Websocket support

Websocket support One of the most attractive features is JSF 2.3 added native websocket support, it means you can write real-time applications with JSF and no need extra effort.
To enable websocket support, you have to add javax.faces.ENABLE_WEBSOCKET_ENDPOINT in web.xml.
<context-param> <param-name>javax.faces.ENABLE_WEBSOCKET_ENDPOINT</param-name> <param-value>true</param-value> </context-param> Hello Websocket Let's start with a simple example.
@ViewScoped@Named("helloBean") publicclassHelloBeanimplementsSerializable { privatestaticfinalLoggerLOG=Logger.getLogger(HelloBean.class.getName()); @Inject@PushPushContext helloChannel; String message; publicvoidsendMessage() { LOG.log(Level.INFO, "send push message"); this.sendPushMessage("hello"); } privatevoidsendPushMessage(Objectmessage) { helloChannel.send(""+ message +" at &…