Hi,
Anybody knows why Hibernate 3.3.1.GA is closing the session when you perform a commit or rollback?

Is there any configuration to change it? Is it a new feature or is a bug?
Any help is welcome.

Thx,
Rodrigo Souza
Campinas - SP
Brazil

See Java Persistence with Hibernate 11.1.2.
"All the data-access code that calls getCurrentSession() on the global shared SessionFactory gets access to the same current Session—if it’s called in the
same thread. The unit of work completes when the Transaction is committed (or rolled back). Hibernate also flushes and closes the current Session and its persistence context if you commit or roll back the transaction. The implication here is that a call to getCurrentSession() after commit or rollback produces a new Session and a fresh persistence context".

I think this is good feature. After commit or rollback Session is in inconsistent state and is not usable, because another transaction can change data in db and persistent context stay in old state in next transaction.