Hi,
I am just investigating the use of Hibernate with EJBs (stateless session only.) The threadlocal pattern looks like the definitive technique to use to grab the appropriate hibernate session (am i correct?!) I was just hoping that a few of you experienced users could help me clarify a few things:

1. I still want to use container declarative transactions in my stateless session beans as per usual - am I right in assuming I can do this? In which case, I guess I don't need to call the session.beginTransaction() etc, right? So is it really as simple as just grabbing the session from my HibernateSessionUtil helper when needed and calling the (eg) save method for my object?

2. I guess I simply close the session at the end of my transacion in the stateless session bean, with nothing more to do than that? (ie no commit as it's container-handled)

3. Does all still work fine with nested EJB calls?

If there's any good documentation out there as to setting this kinda thing up (I'm sure loads of people must need to do it!) please feel free to drop a few URLs into a reply!

thanks loads!
mike

1. using the Transaction API is optional if you use CMT
2. Yes, but you have to manually do session.flush()
3. No rpoblem, as long as it is inside of one thread.

thanks for the quick reply!

re: 3, under what circumstances would a nested EJB call not be within the same thread and cause problems?

also, would the sample HibernateUtil helper class included in the reference guide be adequate for a J2EE implementation as described? (I have seen various more complex implementations for a J2EE implementation but am not sure if they're necessary)

thanks again

Which Application Server do you use?
I use Weblogic Application Server and ThreadLocal does not work with it.

Could you please send your ThreadLocal implementation to me? I just want to check if I've made mistake in my work.

Regards,
Amin Emami

It must work in the same way as method parameter for local beans, it is designed to emulate method parameter (JVM allocates stack for parameters and local variables per thread too).
Stateful bean can be used to propagate remote transactions, but you need to create bean per thead on client (it can be assigned to threadlocal too).