Hello,

For our application I'm coming to believe that Session level caching is not really essential. We've actually had to resort systematic session.clear() after rollbacking the underlying Transaction.

I'm wondering if anyone else has come across this ?

Is there a simple way to disable session level caching (without prodiving a Custom SessionFactory) ?

Thanks.

Alain.

The longer you keep you sessions alive the more likely you are going to use a session.clear(). In general, it is best to keep your sessions alive for short periods of time thus a rollback would, in many cases, represent the end hence the session gets thrown away. As far as the cache is concerned this is equivalent to clearing it.

Assuming the rollback is caused by a DB error - hasn't Gavin said not to to continue using a Session after an exception?

Or am I confused again?

You are correct. The issue is that the session cache is (possibly/likely) in an inconsistent state thus you cannot continue to use it and guarantee data integrity. If the session cache is cleared then this issue not longer applies.