The Hibernate documentation recommends closing the Session and opening a new one when a HibernateException is thrown.

But Spring 1.2 calls Session.clear() when it rollbacks the transaction.
Is that sufficient to reset the Session to a consistent (ie. empty) state that allows it to be reused in a new transaction?

Thanks.

Then don't use Spring, easy.

I wasn't asking whether Spring calling Session.clear() causes problems.

What I was asking is whether an application can reliably use a Session in a new transaction after calling Session.clear() and rolling back the original transaction.

No! That's why the Hibernate _reference_ is quite clear on it.

Thanks. It would be helpful if you could describe the kinds of problems that are not solved by causing Session.clear().

Check the source code.

Christian,

I know that you are incredibly busy but it would be extremely helpful if you could spend a minute or two describing some of the problems that can occur if an application continues to use a session after an exception is thrown.

Thanks

Chris

Dude, here's the thing. It may well be that *no* problems will occur (I will have to check the code myself). But that is completely irrelevant. Hibernate defines a lifecycle for the Session. I assume that lifecycle when I change the code of Hibernate. So if you don't want a future version of Hibernate to break your application, you should obey the lifecycle we define.