Hi ... Myself and colleague are introducing Hibernate to our new projects. We have been doing a lot of reading and i personally have tried a number of hibernate tutorials now for over 6 months and he is only the hibernate ship now. We kinda stumbling over the issue of whether to use Dedicated transaction manager or just a straight use of session.beginTransaction(). Our application is a simple CRUD web based and will use struts 1.3 and HIbernate (no experience of other frameworks such as spring). The other battle is whether to follow the ThreadLocal pattern which i support fully, but he doesn't because he believes tomcat cannot work in such environment. He seem to think is not recommended from hibernate.org anymore (ver 3.2-3.3) as it is complex and old perhaps ... Is it not recommended to use ThreadLocal pattern anymore?

Thanks in advance

My sugestion if instead you use the threadlocal object... which leads the code to be hard to read... you store your shared objects on ConcurrentHashMap for example(depending the number of users of your app you even notice any performance issue)... check this class implementation...
ThreadLocal pattern. is recommended to use with 'context' - 'configuration' like objects... (check jbpm implementation of configuration and context object.). Also if you configure your session (current_session_context_class) to thread hibernate will use the threadlocal to store it... is that assumption correct ?

regards.

Not sure what you mean by 'contex' but if i set this parameter


from hibernate.cfg.xml file, does that mean i should now use the ServletFilter to get the currentSession on threadLocal?

No, this means that hibernate session will be stored on a thread local object.

org.hibernate.context.ThreadLocalSessionContext.

which leads with some tricks to take care of unbind the current session at end of the request. if you work with autocommit sessions.. .. you dont have worry about.
but autocommit :P is fun when you talk about hibernate.


Regards.