Partner – JPA Buddy – NPI (tag=JPA/Hibernate)
announcement - icon

The right tools can and will save a lot of time. As long as you are using Hibernate and IntelliJ IDEA you can boost your coding speed and quality with JPA Buddy. It will help in a lot of the day-to-day work:

  • Creating JPA entities that follow best practices for efficient mapping
  • Creating DTOs from entities and MapStruct mappers using convenient visual tools
  • Generating entities from the existing database or Swagger-generated POJOs
  • Visually composing methods for Spring Data JPA repositories
  • Generating differential SQL to update your schema in accordance with your changes in entities
  • Autogenerating Flyway migrations and Liquibase changelogs comparing entities with the database or two databases
  • … and a lot more

Simply put, you'll learn and use the best practices of Hibernate and surrounding technology and become a lot more!

Definitely visit the JPA Buddy site to see its features in action closer.

Course – LSD (cat=Persistence)

Get started with Spring Data JPA through the reference Learn Spring Data JPA course:


1. Overview

In the context of ORM, database auditing means tracking and logging events related to persistent entities, or simply entity versioning. Inspired by SQL triggers, the events are insert, update, and delete operations on entities. The benefits of database auditing are analogous to those provided by source version control.

In this tutorial, we'll demonstrate three approaches to introducing auditing into an application. First, we'll implement it using standard JPA. Next, we'll look at two JPA extensions that provide their own auditing functionality, one provided by Hibernate, another by Spring Data.

Here are the sample related entities, Bar and Foo, that we'll use in this example:


2. Auditing With JPA

JPA doesn’t explicitly contain an auditing API, but we can achieve this functionality by using entity lifecycle events.

2.1. @PrePersist, @PreUpdate and @PreRemove

In the JPA Entity class, we can specify a method as a callback, which we can invoke during a particular entity lifecycle event. As we're interested in callbacks executed before the corresponding DML operations, the @PrePersist, @PreUpdate and @PreRemove callback annotations are available for our purposes:

public class Bar {
    public void onPrePersist() { ... }
    public void onPreUpdate() { ... }
    public void onPreRemove() { ... }

Internal callback methods should always return void, and take no arguments. They can have any name and any access level, but shouldn't be static.

Be aware that the @Version annotation in JPA isn't strictly related to our topic; it has to do with optimistic locking more than with audit data.

2.2. Implementing the Callback Methods

There's a significant restriction with this approach though. As stated in JPA 2 specification (JSR 317):

In general, the lifecycle method of a portable application should not invoke EntityManager or Query operations, access other entity instances, or modify relationships within the same persistence context. A lifecycle callback method may modify the non-relationship state of the entity on which it is invoked.

In the absence of an auditing framework, we must maintain the database schema and domain model manually. For our simple use case, let’s add two new properties to the entity, as we can manage only the “non-relationship state of the entity.” An operation property will store the name of an operation performed, and a timestamp property is for the timestamp of the operation:

public class Bar {
    @Column(name = "operation")
    private String operation;
    @Column(name = "timestamp")
    private long timestamp;
    // standard setters and getters for the new properties
    public void onPrePersist() {
    public void onPreUpdate() {
    public void onPreRemove() {
    private void audit(String operation) {
        setTimestamp((new Date()).getTime());

If we need to add such auditing to multiple classes, we can use @EntityListeners to centralize the code:

public class Bar { ... }
public class AuditListener {
    private void beforeAnyOperation(Object object) { ... }

3. Hibernate Envers

With Hibernate, we can make use of Interceptors and EventListeners, as well as database triggers, to accomplish auditing. But the ORM framework offers Envers, a module implementing auditing and versioning of persistent classes.

3.1. Get Started With Envers

To set up Envers, we need to add the hibernate-envers JAR into our classpath:


Then we add the @Audited annotation, either on an @Entity (to audit the whole entity) or on specific @Columns (if we need to audit specific properties only):

public class Bar { ... }

Note that Bar has a one-to-many relationship with Foo. In this case, we either need to audit Foo as well by adding @Audited on Foo, or set @NotAudited on the relationship’s property in Bar:

@OneToMany(mappedBy = "bar")
private Set<Foo> fooSet;

3.2. Creating Audit Log Tables

There are several ways to create audit tables:

  • set to create, create-drop, or update, so Envers can create them automatically
  • use org.hibernate.tool.EnversSchemaGenerator to export the complete database schema programmatically
  • set up an Ant task to generate appropriate DDL statements
  • use a Maven plugin for generating a database schema from our mappings (such as Juplo) to export Envers schema (works with Hibernate 4 and higher)

We’ll go the first route, as it's the most straightforward, but be aware that using isn't safe in production.

In our case, the bar_AUD and foo_AUD (if we've set Foo as @Audited as well) tables should be generated automatically. The audit tables copy all audited fields from the entity's table with two fields, REVTYPE (values are: “0” for adding, “1” for updating, and “2” for removing an entity) and REV.

Besides these, an extra table named REVINFO will be generated by default. It includes two important fields, REV and REVTSTMP, and records the timestamp of every revision. As we can guess, bar_AUD.REV and foo_AUD.REV are actually foreign keys to REVINFO.REV.

3.3. Configuring Envers

We can configure Envers properties just like any other Hibernate property.

For example, let's change the audit table suffix (which defaults to “_AUD“) to “_AUDIT_LOG.” Here's how we set the value of the corresponding property org.hibernate.envers.audit_table_suffix:

Properties hibernateProperties = new Properties(); 
  "org.hibernate.envers.audit_table_suffix", "_AUDIT_LOG"); 

A full listing of available properties can be found in the Envers documentation.

3.4. Accessing Entity History

We can query for historic data in a way similar to querying data via the Hibernate Criteria API.  We can access the audit history of an entity using the AuditReader interface, which we can obtain with an open EntityManager or Session via the AuditReaderFactory:

AuditReader reader = AuditReaderFactory.get(session);

Envers provides AuditQueryCreator (returned by AuditReader.createQuery()) in order to create audit-specific queries. The following line will return all Bar instances modified at revision #2 (where bar_AUDIT_LOG.REV = 2):

AuditQuery query = reader.createQuery()
  .forEntitiesAtRevision(Bar.class, 2)

Here's how we can query for Bar‘s revisions. It'll result in getting a list of all audited Bar instances in all their states:

AuditQuery query = reader.createQuery()
  .forRevisionsOfEntity(Bar.class, true, true);

If the second parameter is false, the result is joined with the REVINFO table. Otherwise, only entity instances are returned. The last parameter specifies whether to return deleted Bar instances.

Then we can specify constraints using the AuditEntity factory class:


4. Spring Data JPA

Spring Data JPA is a framework that extends JPA by adding an extra layer of abstraction on the top of the JPA provider. This layer supports creating JPA repositories by extending Spring JPA repository interfaces.

For our purposes, we can extend CrudRepository<T, ID extends Serializable>, the interface for generic CRUD operations. As soon as we've created and injected our repository to another component, Spring Data will provide the implementation automatically, and we're ready to add auditing functionality.

4.1. Enabling JPA Auditing

To start, we want to enable auditing via annotation configuration. In order to do that, we add @EnableJpaAuditing on our @Configuration class:

public class PersistenceConfig { ... }

4.2. Adding Spring's Entity Callback Listener

As we already know, JPA provides the @EntityListeners annotation to specify callback listener classes. Spring Data provides its own JPA entity listener class, AuditingEntityListener. So let's specify the listener for the Bar entity:

public class Bar { ... }

Now we can capture auditing information by the listener upon persisting and updating the Bar entity.

4.3. Tracking Created and Last Modified Dates

Next, we'll add two new properties for storing the created and last modified dates to our Bar entity. The properties are annotated by the @CreatedDate and @LastModifiedDate annotations accordingly, and their values are set automatically:

public class Bar {
    @Column(name = "created_date", nullable = false, updatable = false)
    private long createdDate;

    @Column(name = "modified_date")
    private long modifiedDate;

Generally, we move the properties to a base class (annotated by @MappedSuperClass), which all of our audited entities would extend. In our example, we add them directly to Bar for the sake of simplicity.

4.4. Auditing the Author of Changes With Spring Security

If our app uses Spring Security, we can track when changes are made and who made them:

public class Bar {
    @Column(name = "created_by")
    private String createdBy;

    @Column(name = "modified_by")
    private String modifiedBy;

The columns annotated with @CreatedBy and @LastModifiedBy are populated with the name of the principal that created or last modified the entity. The information comes from SecurityContext‘s Authentication instance. If we want to customize values that are set to the annotated fields, we can implement the AuditorAware<T> interface:

public class AuditorAwareImpl implements AuditorAware<String> {
    public String getCurrentAuditor() {
        // your custom logic


In order to configure the app to use AuditorAwareImpl to look up the current principal, we declare a bean of AuditorAware type, initialized with an instance of AuditorAwareImpl, and specify the bean's name as the auditorAwareRef parameter's value in @EnableJpaAuditing:

public class PersistenceConfig {
    AuditorAware<String> auditorProvider() {
        return new AuditorAwareImpl();

5. Conclusion

In this article, we considered three approaches to implementing auditing functionality:

  • The pure JPA approach is the most basic and consists of using lifecycle callbacks. However, we're only allowed to modify the non-relationship state of an entity. This makes the @PreRemove callback useless for our purposes, as any settings we made in the method will be deleted along with the entity.
  • Envers is a mature auditing module provided by Hibernate. It's highly configurable and lacks the flaws of the pure JPA implementation. Thus, it allows us to audit the delete operation, as it logs into tables other than the entity's table.
  • The Spring Data JPA approach abstracts working with JPA callbacks and provides handy annotations for auditing properties. It's also ready for integration with Spring Security. The disadvantage is that it inherits the same flaws of the JPA approach, so the delete operation can't be audited.

The examples for this article are available in a GitHub repository.

Course – LSD (cat=Persistence)

Get started with Spring Data JPA through the reference Learn Spring Data JPA course:

res – Persistence (eBook) (cat=Persistence)
Comments are closed on this article!