CODEWITHSUNDEEP
javaspringhibernate
Matthew Stopa
Matthew Stopa

Reputation: 3875

Benefits of using Springs Transaction management vs using hibernate

I've been trying to learn spring and hibernate, and I've used a lot of examples around the net to put together a nice application. However, I realized now that Spring supports transaction management. In my spring app I just simply made whatever calls I wanted to, directly to hibernate. Is there a reason/benefit as to why people would use Spring's transaction management/db stuff?

Upvotes: 18

Views: 15362

Answers (2)

Aravind Yarram
Aravind Yarram

Reputation: 80194

The spring's reference doc mentions it very clear

The Spring Framework provides a consistent abstraction for transaction management that delivers the following benefits:

  • Provides a consistent programming model across different transaction APIs such as JTA, JDBC, Hibernate, JPA, and JDO.
  • Supports declarative transaction management.
  • Provides a simpler API for programmatic transaction management than a number of complex transaction APIs such as JTA.
  • Integrates very well with Spring's various data access abstractions.

Provides a consistent programming model across different transaction APIs such as JTA, JDBC, Hibernate, JPA, and JDO.

Let us say you are currently using hibernate api for transaction management and sometime down the road you would want to switch to JDO. This requires the change of transaction management code. If you use Spring then there is no change.

Supports declarative transaction management.

Similar to EJB

Provides a simpler API for programmatic transaction management than a number of complex transactions APIs such as JTA.

JTA and JDBC have different APIs for transaction management. Spring abstracts that out by providing a uniform API.

Upvotes: 10

axtavt
axtavt

Reputation: 242786

The real advantages are:

  • Lightweight declarative syntax. Compare:

    public void saveEmployee(Employee e) {
    Session s = sf.getCurrentSession();    
    s.getTransaction().begin();
    s.save(e);    
    s.getTransaction().commit();
}

    and

    @Transactional
public void saveEmployee(Employee e) {
    sf.getCurrentSession().save(e);
}

  • Flexible transaction propagation. Imagine that now you need to execute this saveEmployee() method as a part of a complex transaction. With manual transaction management, you need to change the method since transaction management is hard-coded. With Spring, transaction propagation works smoothly:

    @Transactional
public void hireEmployee(Employee e) {
    dao.saveEmployee(e);
    doOtherStuffInTheSameTransaction(e);
}

  • Automatic rollback in the case of exceptions

Upvotes: 26

Related Questions