Session/Transaction code: where to put it?

Laurens · **Joined:** Wed Apr 05, 2006 3:19 pm **Posts:** 43

Code:

hibernateUtil.get.......getCurrentSession.beginTransaction();
hibernateUtil.get.......getCurrentSession.getTransaction().commit();
hibernateUtil.get.......getCurrentSession.flush();
hibernateUtil.get.......getCurrentSession.close();

This is very repetitive code and it appears everywhere in the documentation in all possible forms. In some situations, combination A works, in other situation, you don't have to flush the session, in other situations, you HAVE to flush, but you don't have to close, in other..... and so on, and so on. Sometimes proxies have to be initialized, etc...

Now where exactly does this code belong?

edward.yakop · **Posted:** Wed Apr 12, 2006 3:37 am

The answer is not that simple.

- Are we dealing with long application transaction? Definition of long if an application transaction spans between hibernate transaction.
- Do we want to deal with detached object or open session view (means we will only close the session once the application transaction is finish).

The answer to this question will be very different depending on the answers of these two questions.

Regards,
Edward