1 Reply Latest reply on Oct 12, 2007 8:16 AM by Gabor Nagypal

    Impossible to change versioned object?

    Gabor Nagypal Newbie


      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)

      Do I do something terribly wrong, or is it now impossible to manipulate DB-objects in a nested conversation? If you save a versioned object, the version number will change, it is normal. Why is an exception thrown?