The targetAuditMode
should be used only for fields which are relations. If you don't want an entity to be audited, simply remove the annotation.
Is it possible with Envers to have different audit modes for different concrete derived classes with a common a mapped baseclass?
-
19-07-2023 - |
Pergunta
I have two JPA entities with the same fields, which I want to store in different tables. So I have based them on an abstract common mapped base class to avoid doubling code. Now I want one of these table to be audited, and the other one not. But when I set the one class to audited, Envers creates an _AUD table for both of the derived classes. Even setting the other derived class to audit mode NotAudited, its audit table is created. Is there a possibility to configure it as described?
My (simplified) classes:
@MappedBaseClass
@Inheritance(strategy=InheritanceType.TABLE_PER_CLASS)
public abstract class AbstractPrice {
// some fields and some methods
}
@Entity
@Audited(targetAuditMode=RelationTargetAuditMode.AUDITED)
public class Price extends AbstractPrice {
}
@Entity
@Audited(targetAuditMode=RelationTargetAuditMode.NOT_AUDITED)
public class OriginalPrice extends AbstractPrice {
}
Solução
Licenciado em: CC-BY-SA com atribuição
Não afiliado a StackOverflow