Red Hat
Sep 8, 2011
by Adam Warski

Some Envers uses had problems because of the limited flexibility in specifying which fields from superclasses (especially those annotated with @MappedSuperclass) should be audited or not. We improved a bit in the latest release, by being able to explicitly enumerate the superclasses to audit.

But still this is not fully flexible. That’s why Ɓukasz Antoniak started a discussion on the Envers forum ( to gather remarks and use-cases on how people use Envers with inheritance. Your opinion will be very valuable to us, so please share!