Hi,
I'm using Hibernate version 3.2.0.ga with Hibernate Annotations 3.2.1.ga.
We have a requirement to perform multiple operations as seperate transaction (independently).
The database I'm using is Oracle9i.
That is those operations can be partially successful (even if subsequent operation(s) fail, we don't want to rollback).
That is we are trying to implement one-session-multiple-transactions [anti]pattern. I understand THIS IS AN ANTI PATTERN AND SHOULD BE USED ONLY IN EXCEPTIONAL SCENARIOS.
I've read both:
http://www.hibernate.org/42.html and
http://www.hibernate.org/43.html
But could not get any simple workaround.

We do use Spring IOC to instantiate Hibernate sessionFactory bean (using org.springframework.orm.hibernate3.annotation.AnnotationSessionFactoryBean class) and
and transactionManager bean (using org.springframework.orm.hibernate3.HibernateTransactionManager class).

What is the simplest solution to have:
======== Session01_BEGIN=======
begin Transaction01
doOperation01()
end Transaction01

begin Transaction02
doOperation02()
end Transaction02
======== Session01_END======

Hibernate gurus, any help is appreciated.

well if you are outside a container
Transaction tx = session.beginTransaction();
//do stuffs
tx.commit();


tx = session.beginTransaction();
//do stuffs
tx.commit();

I don't know how to handle that with spring though

Hi,

i have simillar scenario -- I always want to write an "attempt" into a db, even on error.

I just did the same emmanuel has said. I use 'session-per-request' pattern.

Depending on your transaction management (i use both -- programatical as well as transaction proxies) you just simply obtain the referencies to your DAOs and do the work in two different transaction.

Just make sure to test your data to know if there will be/will not be a database error. (In case of db error your session will get closed.)

I always deploy transactional and non-transactional DAO to allow me whatever combination i preferer.

m.

Thanks Mar.

Your approach appears to be the quickest solution for my situation.

We are also exploring using "Catch the exceptions before Hibernate/Spring sees them" approach as well. Simply, we are intending to catch exceptions for each DB-Transactions. Effectively, Hibernate/Spring does not encounter any exceptions and doesn't try to roll-back