Hi,

We're using envers 3.6.10.Final as our auditing solution. I have a question about the way envers audits the other side of a bidirectional relationship regardless of whether any changes have been made to it.

For example :

I have a simple many-to-many bidirectional relationship between Person and DistributionList

When persisting a DistributionList with a collection of Person, envers audits the DistributionList entity, the join table but also the Person entity.

This means that when we inspect audit information on the Person entity, (forRevisionsOfEntity method), we find that there is a revision every time a person has been added/removed from a DistributionList. Consequently, when displaying audit information for the Person entity, numerous revisions are exactly the same.

Is there anyway to stop envers from doing this? targetAuditMode=RelationTargetAuditMode.NOT_AUDITED seems to have zero effect on what is written to the audit tables.

Thanks in advance.

Hi,

I had the same problem with a bidirectional many-to-many relation. My case was actually vene worse because one of the classes was abstract with a discriminator value.
The instances of this abstract class were audited when I added the class to the other's collection, but the discriminator showed the wrong value.
I was able to fix it by specifying NotAudited on one side of the many-to-many relation, and keeping the auditing on the owning side.
Hope this helps. BTW, we are using hibernate envers 3.6.9.

Regards,

Frank.