Adam Warski

8 Sep 2011

How to handle inheritance and @Audited?


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!


comments powered by Disqus

Any questions?

Can’t find the answer you’re looking for?