I want to use 2 functions with in each a transaction.

A() {
HibernateUtil.beginTransaction();
fctA();
HibernateUtil.commitTransaction();
}

B() {
HibernateUtil.beginTransaction();
fctB();
HibernateUtil.commitTransaction();
}

If I call A or B in a Session, no problem.
But if I call A and B in the same session, the commit in function B() commit the 2 transactions.

So I modified functions as follows:

A() {
HibernateUtil.currentTransaction();
fctA();
}

B() {
HibernateUtil. currentTransaction();
fctB();
}

Now, only one transaction is manipulated, but I don't known where to do the call to commit.
A and B are not transaction, because there are no commit in it.

http://www.dotnetguru.org/articles/doss ... apping.htm talk about a ServiceLocator to commit all transaction.

Thanks a lot for your answers.

You may want to check the Spring framework. That will give you the opportunity to use declarative transactions instead of separating them programatically.
Another solution is to have 2 different layers let's call them service and DAO. In services you would explicitly commit/rollback transactions while in DAO you will not have any transaction code. Passing the connection can be done with a ThreadLocal variable so as you do not polute the DAO code with Connection objects in each methods.

Yes for Services and DAO, but normaly all Hibernate code is in DAO object.
And the transaction code is the DAO object, but commit too, and this is my problem.

All transaction code isn't in the DAO.
I use a service to do the transaction.

Service {
executeTransaction() {
HibernateUtil.beginTransaction();
A();
B();
C();
HibernateUtil.commitTransaction();
}
}

But if in B function, user want to do a transaction, A and B are commited.
I want to commit just B.

The DAOs will not have any transaction code.
You will just have to add a new method in Service for each behaviour you have:

m0{
A();
B();
}

m1{
A()
}

m2{
B()
}

in begin/end of methods you will have to add the commit/rollback code.