Why is the scope of a transaction different than the scope of a session? In other words, why can I have multiple transactions on a single session?

I don't really see a use case where it would be safe to have several transactions on a single session since a transaction commit will flush the session, possibly committing changes to dirty objects. Those that ever tried "open session in view" know that this can lead to all kinds of unwanted side effects.

It seems that to be save and deterministic you should begin a transaction when you create a session and close the session again when the transaction is committed or rolled back (for rollback the docs clearly state that you should throw away the session). Is this a best practice?

Erwin

Anybody? This must be a pretty dry question :-)

that something isnt good in all cases doesnt mean it shouldnt be possible ,)

but anyhow...having a long session with multiple short transactions is in some cases a good thing when having a well defined application transaction.

I know that this scenario in some cases are very usefull in e.g. swing applications. (together with some clever usage of evict,refresh etc.)