Hi,
I try to work on a legacy application and turn it into a hibernate+jpa driven project from a pure jdbc one. But I have some questions right now,

i use hibernate.current_session_context_class=thread as session manager

but the session goes out between two thread, and I can't not pass bean between then. One solution i can think is that i detach all objects when 1st thread end and reload them in 2nd thread. but i wonder if there is a better solution.

Or in general, shall i change the design a bit to avoid cross thread boundaries with state?

Any ideas will be grateful!
Thx!

no one reply?? please..

I personally prefer to use

instead to

which corresponds to manual persistence-propagation.
Obviously you then have to pass the returned session between the threads,
I don't understand if you can do this and if it is what you mean with 'cannot pass bean between then'.


There are different ways to implement Conversations with Hibernate
(also depending if you use JPA or not, Java SE or J2EE container, etc.).
The book 'Java Persistence with Hibernate' spends a whole chapter (11.2) in this topic,
so it is hard to explain solutions here in few lines.

I am confused between sf.openSession() and sf.getCurrentSession().

If we use sf.openSession() within the same thread twice, do we get two different sessions with in that thread?
If it returns the same session within the same thread for any number of calls, how hibernate keep track of the session it supplied initially?

I know in sf.getCurrentSession, first time it binds the session to current thread, so every subsequent request with in that thread will return the same.

Thanks in advance

YES
It is you job to save the returned session into a variable and use it until your unit of work terminates.

Correction:
It is your job to keep the returned session into a variable, use this variable and close the session explicitly once you not need it anymore.

Thanks, it clears my confusion