• 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 Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

why we define Session as ThreadLocal in hibernate

 
Greenhorn
Posts: 11
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hello

I am learning Hibernate I just want to know why we define session object as ThreadLocal what is the advantage? what is the disadvantage if we don't make it as ThreadLocal

and one more SessionFactory is only one instance per application/VM ? is there any way ther is more than one SesionFcatory


thanks for your help
 
author and cow tipper
Posts: 5009
1
Hibernate Spring Tomcat Server
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
ThreadLocal is just an easy way to package up the thread and allow an application to do programatic transaction demarcation using the Hibernate libraries. It's basic, but it's functional.

Just have one session manager. Sometimes when you go to two database, you may need two session factories, but really you only need one.

-Cameron McKenzie
reply
    Bookmark Topic Watch Topic
  • New Topic