Hi.
What are the best designs to have this "initialization" code?


The createDataStore() and storeClass() methods can be called only once for the application.
So I could call it on some kind of filter at the first request of my application for example. Right?

About the buildSessionFactory() method, can I call it only once for the application? And leave the sf obejct there available forever?

The openSession() method I could call before all my façade method just before the database access logic, right?

Thanks.

Hibernate version:anyone

Mapping documents:don`t apply

Code between sessionFactory.openSession() and session.close():don`t apply

Full stack trace of any exception that occurs:don`t apply

Name and version of the database you are using:doesn`t matter really

Yes, that's one approach. In simple applications I've used the same filter for both the Open-Session-In-View and the initialization, with configuration ocuring during static initialization of the filter.

In practice, configuration can be a pain and for large scale applications an IOC container like Spring or HiveMind can be very helpful in configuring Hibernate.