• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Ron McLeod
  • Paul Clapham
  • Bear Bibeault
  • Junilu Lacar
Sheriffs:
  • Jeanne Boyarsky
  • Tim Cooke
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • salvin francis
  • Frits Walraven
Bartenders:
  • Scott Selikoff
  • Piet Souris
  • Carey Brown

Design question for creating a DAO using Hibernate

 
Ranch Hand
Posts: 96
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello,

I m creating a DAO using Hibernate.
is it a good idea to create SessionFactory, Session and Transaction Objects as instance fields and initialize them in the Constructor?
should i close the session on every method that interact with the DB?
if not can you suggest a better design?

Thanks
 
Author
Posts: 198
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
No, keep the SessionFactory in a singleton, then get the session using sessionFactory.getCurrentSession() to get the current session for the thread that you're in.

Read the first chapter of the Hibernate documentation.

The transaction boundaries depend on how long your transactions are. Typically you manage one per request. In a Web-based app, you might start and end the transaction in a ServletFilter.
 
Sammy Bill
Ranch Hand
Posts: 96
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

Javid Jamae wrote:No, keep the SessionFactory in a singleton, then get the session using sessionFactory.getCurrentSession() to get the current session for the thread that you're in.

Read the first chapter of the Hibernate documentation.

The transaction boundaries depend on how long your transactions are. Typically you manage one per request. In a Web-based app, you might start and end the transaction in a ServletFilter.



Thanks for your Help.
So you mean, get a new session instance from the sessionFactory and a new transaction from the session in every method and i dont need to close them untill i actually use the DAO in a servlet or so??

bsically thats what i have:


Please correct me if i m doing anything wrong.

Thanks again.
 
Ranch Hand
Posts: 36
 
It looks like it's time for me to write you a reality check! Or maybe a tiny ad!
the value of filler advertising in 2020
https://coderanch.com/t/730886/filler-advertising
reply
    Bookmark Topic Watch Topic
  • New Topic