ThreadLocalSessionContext provides on demand session creation - at least in theory. The returned session doesn't work until the user code explicity starts a transaction. So what is user code supposed to do? Request a session and verify if a transaction already started? This seems to defeat the purpose of on demand session creation.

Another thing is that opening and committing a transaction on non-transactional MySQL tables is pure overhead - 2 unnecessary round-trip to the server. Why is this forced? To not forget to close the session context? If my code forget that to explicitly close the ThreadLocalSessionContext then in the same way it can forget to commit or rollback the transaction.

I thought I write my own CurrentSessionContext implementation. But then I noticed that this interface returns a Hibernate 2 Session. Which is compatible with Hibernate 3 Session but contains many deprecated methods. Why does it return the old compatibility interface when it was written for the 3.1 series?


Hibernate version: 3.2.2

Name and version of the database you are using:
MySQL / myisam

It is there to provide a mechanism to get the current session for the life of the current thread. It's useful so you don't have to pass a session reference all around to use the same session. You are still responsible for transaction management.