I have just started to use Hibernate... wonderfully easy to persist and retrieve data... but I need to run it under a webservice server (glue) and I have always done my DAO thru a singleton connection manager... I looked at the ThreadLocal information, and understand what it is doing, but don't know if that is the right implementation for my scenerio...

In my tests with Hibernate, I notice that starting up the process takes quite a bit of time... once running, using it is very fast... should I put the code for the Configuration and SessionFactory in a Singleton and call that from the ThreadLocal class, or just forgo the whole ThreadLocal part and put the SessionFactory in a Singleton and get the sessions from there... although that seems like it would be a bottleneck for scalibility...

Thanks for any input...

JH

It is not a bottleneck. You can also automatically bind a SessionFactory to JNDI (on startup) and retrieve it later everytime you need a Session. A singleton/threadlocal combo looks like this:

http://www.hibernate.org/114.html

Oh, this example needs some "synchronize" :)