I just want to make sure this is consistent across uses. What are the
rules for Audited, MappedSuperclass and Entity? IMO, that is what should
happen for Audited, MappedSuperclass and Embeddable as well. Are those
consistent?
Adam, what specifically is complicated by supporting AO paths? Is it
Hi Adam,
Currently, the ways to enable auditing on a mapped-superclass that we
discussed below do not work when an embeddable class has no declared data. The
only way I can find to enable auditing for the mapped-superclass is to annotate
the embeddable class with @Audited.
For example:
@Enti
Sorry, no idea why I missed that email.
So the basic rule is:
- fields from a non-audited mapped superclass are never audited, unless an
@AuditOverride is specified
- if the mapped superclass is audited, then its fields are of course audited as
well
I don’t think we want to get into supporting
