I'm terribly sorry for posting this question again, but my other was ignored... :-(

n our system here, which has several entities and relationships, everything was running fine (unit tests, etc.). We are using the following hibernate versions:

Hibernate Core 3.2.0.cr4
Hibernate Annotations 3.2.0.cr2
Hibernate EntityManager 3.2.0.cr2

But i also tested in:

Hibernate Core 3.2.1.GA
Hibernate Annotations 3.2.0.GA
Hibernate EntityManager 3.2.1.GA


We are using annotations for everything, including validation.

We then tried to use Hibernate @Version annotation to control concurrency. Everything was working fine, and right after i insert this annotation in the proper field, many of my unit tests start accusing this error, in unused collections:

org.hibernate.AssertionFailure: collection [...] was not processed by flush()

We are not using any custom listeners. On the internet, i checked that custom listeners may cause this trouble, but in our case we only need to put versioning for it to happen.

---

I found a way for this error not to happen, but it is not a desirable way:

Entities X and Y have a bidirectional many-to-many relation. If i use @Version, when testing X i get "collection Y.x was not processed by flush()". But if i set the Fetch Type in collection X.y to EAGER, this error does not happen.

Why doesn't it work with lazy? Is it a hibernate bug?

I still have the same problem... :-(

I really have the same problem !

we have m : n relationship with between USER and GROUP, as also 1 : n between GROUP and PERMISSION.
If we update Group or Permissions, it throws an assertionfailure for collection USER.groups.



These error occures really only in following constellation: ManyToMany + @Version-Column + Flush-Event.

Seems really like a hibernate-bug.[/code]