Conditional Auditing through class-level annotations
Description
Activity
Daniel KrausDecember 5, 2023 at 9:39 PM
The idea of an @AuditListener annotation is great! Unfortunately, it appears to still be an idea? 
As described above, the current approach is quite intrusive. I assume most users end up copying the EnversIntegrator and then start customizing it, e.g., by using their own listeners where necessary.
I wonder if an intermediate, backwards-compatible solution would be feasible. Would it make sense to have protected methods for each (relevant) EventType inside EnversIntegrator? Something like:
public class MyEnversIntegrator extends EnversIntegrator {
@Override
protected PostDeleteEventListener postDelete() {
return new MyPostDeleteEventListenerImpl();
}
}This still requires the implementation of listeners, but would relief users from the burden of copying code (and having to remember that when upgrading Hibernate/Envers).
Note: setting hibernate.envers.autoRegisterListeners = false would require MyEnversIntegrator to “somehow” ignore that property, as the base class / EnversIntegrator wouldn’t integrate.
Chris CranfordDecember 9, 2016 at 2:21 AMEdited
Based on discussion from http://stackoverflow.com/a/41052120/1572269 and most recently http://stackoverflow.com/a/41754018/1572269
Details
Assignee
Chris CranfordChris CranfordReporter
Chris CranfordChris CranfordComponents
Fix versions
Priority
Major
Details
Details
Assignee
Reporter
Components
Fix versions
Priority
Major
The current conditional auditing solution works but its somewhat intrusive. It requires users to register their own Hibernate listeners and implement their own hooks on whether to audit a particular entity or not. This works, but such a solution could easily be standardized.
Consider the notion of introducing a new annotation,
@AuditListener. This annotation is much like its JPA counterpart,@EventListener. The annotation allows specifying a class that is to act as a callback mechanism.The various methods of the specified class allow users to inspect the state of the entity during the various event life cycles used by Envers. The code users were expected to put inside the custom event listeners can now be moved to these callback classes instead, eliminating users from having to manipulate with event listener registration.