Hi,
When I have a versioned Hibernate object in a nested conversation, it is impossible to save it because Seam automatically passivates the object, tries to activate it at the end of the conversation, and notices that the version number has been changed, and throws an exception:
org.hibernate.StaleStateException: current database version number does not match passivated version number
at org.jboss.seam.persistence.HibernatePersistenceProvider.checkVersion(HibernatePersistenceProvider.java:277)
I forgot to mention that I use Seam 2 CR2, Hibernate persistence with Seam-managed transactions.