Question

I just followed a simple hibernate struts tutorial and succesfully made db calls through hibernate. However I don’t see the code closing the hibernate connection anywhere.

sessionFactory.getCurrentSession();

is used to get the session per request. Should I close this session when the user logs out? or after each request of is this something taken care of by the framework?

a second related question is, In what kind of use case would I use a hibernate session interceptor?

and a third question(sorry it just popped in my mind) what the best option for caching with hibernate/struts2?

Answer 1

Regarding the first question, the reference documentation says:

A org.hibernate.Session begins when the first call to
getCurrentSession() is made for the current thread. It is then bound
by Hibernate to the current thread. When the transaction ends, either
through commit or rollback, Hibernate automatically unbinds the
org.hibernate.Session from the thread and closes it for you.

Regarding your second question, the documentation says:

The Interceptor interface provides callbacks from the session to the
application, allowing the application to inspect and/or manipulate
properties of a persistent object before it is saved, updated, deleted
or loaded. One possible use for this is to track auditing information.
For example, the following Interceptor automatically sets the
createTimestamp when an Auditable is created and updates the
lastUpdateTimestamp property when an Auditable is updated.

Regarding the third question, Struts2 is a presentation framework. It has nothing to do with persistence and thus caching of the persistent entities. The documentation talks in details about the second-level cache.

As you see, the documentation has a whole lot of interesting information. I would advise reading it.