Hi!
I have a problem with Envers and Embedded Collections. The problem is that when I add two embeddable value objects to my entity in a single revision the history don't have a way to differ between the two value-objects, so it uses the entity-id to keep track of whats happend, and a NonUniqeObjectException is thrown. Shouldn't the database hold the key to the parent and perhaps a hashcode from the value-object to avoid this problem?
I found a couple of StackOverflow-questions that seems to be in the same subject.
http://stackoverflow.com/questions/16507596/auditing-elementcollection-embeddable-with-hibernate-envers http://stackoverflow.com/questions/18607422/auditing-embeddable-elementcollection-with-hibernate-envers
Does Envers really support ElementCollection?
Thanks in advance
|