Hi,

This is the code for the disconnectSession() at HibernateUtil in the latest CaveatEmptor example.



My question is, instead of threadSession.set(null), shouldn´t be





Because if it is threadSession.set(null), when we call the getSession, it will open a new session.

I don´t know if I missed something, but it is what I understood when you sugested the disconect() for the Long session at the Hibernate in action...

Thank you in advance
Pedro Henrique

You simply don't call getSession() after disconnectSession() without doing a reconnectSession() first. You have to null out the threadlocal variable.

Thanks for the quick reply Christian.

That was what i was missing ...


About this:



Why do I have to null out the threadlocal variable? I mean in your example I see why, because the way you work with the reconnection. But what about if I want to make the reconnect(), reconect the session from the ThreadLocal variable, and the disconnect() disconect this session but not null out the variable , wich would only be done when I call closeSession().It would be a problem?

Thanks again.
Pedro Henrique

I don't know what you want.