I'm using nHibernate 2.0 in a winform app and have the following scenario:

Session 1: Used to load a entity, Session 1 closed

Entity bound to screen, user interacts with it and its collections

Session 2:
- Transaction started
- Entity associated to session with SaveOrUpdate
- Flush happens (actually triggered by a query)
- After the flush I notice the version numbers are incremented on dirty entities
- Business Rules evaluated and one fails
- Transaction Rolled Back
- Session Closed

User sees message and fixes problem in Entity (same one still bound)

Session 3:
- Transaction Started
- Flush happens (again triggered by a query)
- Notice version numbers incremented again on dirty entities
- Business Rules evaluated and all pass
- Transaction Committed:
--> Stale Data Exception on account of the version numbers having been incremented twice

What is the recommended way around this? I know I can reload the entities and reapply user changes in code but I'd like to get a generic solution as this will happen throughout the application with entities over varying complexity and object graph depth.

Thanks in advance.

I have the same question. Seems related to this topic: http://forum.hibernate.org/viewtopic.php?t=942461