Why we use sessionfactory

During application startup, this is created and is kept for usage. It is a thread-safe object used by the threads of the application. Exception in thread "main" org.

The session object gets closed, once the sessionFactory gets closed. Session objects of hibernate are never thread safe. Also, it is relatively faster to open a new session. Example for Hibernate SessionFactory is given below : package com. SessionFactory; import org. HibernateUtility; import org. The two threads call the factory method of factory at the same time, which makes it possible for creating objects of hibernate SessionFactory.

A sessionFactory object represents a single database or datastore. It is a thread safe object. I'm Nataraja Gootooru, programmer by profession and passionate about technologies.

All examples given here are as simple as possible to help beginners. The source code is compiled and tested in my dev environment.

If you come across any mistakes or bugs, please email me to [email protected]. As you know, destory is part of servlet life cycle methods, it is used to kill the servlet instance. Servlet Engine is used to call destory.

In case, if you call destory method from service , it just execute the code written in the destory , but it wont kill the servlet instance. About Author I'm Nataraja Gootooru, programmer by profession and passionate about technologies. So that in Hibernate SessionFactory , a configuration file and all the mapping data will be stored. In real time applications like spring with hibernate integration , per each client request if a separate SessionFactory is created then the performance of the application will be reduced.

To implement the Hibernate SessionFactory as a singleton, we create a separate class. Because this class is only responsible for making the Hibernate SessionFactory object as a singleton. Usually, we call such type of classes as utility classes. In that utility class, we define a static factory method to a Hibernate SessionFactory object for one time and return the same factory object always.

Since the utility class is only responsible for creating the singleton Hibernate SessionFactory object and returning that object, there is no need for creating an object for utility class.

It is available for the whole application while a Session is only available for particular transaction. Session is short-lived while SessionFactory objects are long-lived. SessionFactory provides a second level cache and Session provides a first level cache. SessionFactory is an interface. SessionFactory can be created by providing Configuration object, which will contain all DB related property details pulled from either hibernate.

SessionFactory is a factory for Session objects.