-->
These old forums are deprecated now and set to read-only. We are waiting for you on our new forums!
More modern, Discourse-based and with GitHub/Google/Twitter authentication built-in.

All times are UTC - 5 hours [ DST ]



Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 1 post ] 
Author Message
 Post subject: session-per-req-with-detached-obj VS session-per-conv
PostPosted: Sat Apr 19, 2014 4:20 pm 
Newbie

Joined: Sat Apr 19, 2014 4:10 pm
Posts: 2
Hi Folks,

I have been working with Hibernate for more than 5 years now and only now started reading its fundamentals. I am currently reading long conversations. I can't understand what does it mean to disconnect the session from the Database (as is the case in session-per-conv) and how is it different from closing the session altogether and create a new one for the next user request (as is the case in session-per-req-with-detached-obj).

Basically why would I keep a session that is disconnected from the DB anyway? And why is this the preferred way as suggested by the documentation.

Thanks for your time (I may have follow up questions).


Top
 Profile  
 
Display posts from previous:  Sort by  
Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 1 post ] 

All times are UTC - 5 hours [ DST ]


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
cron
© Copyright 2014, Red Hat Inc. All rights reserved. JBoss and Hibernate are registered trademarks and servicemarks of Red Hat, Inc.