I have two entity's "Application" and "ApplicationDocument"
Table 1
@Entity
@Table(name = "applications")
@EntityListeners(AuditingEntityListener.class)
public class Application {
@Id
@GeneratedValue(strategy = GenerationType.AUTO)
private Long id;
@Audited
private String title;
@OneToMany(mappedBy = "application")
@JsonManagedReference
@AuditJoinTable
private List<ApplicationDocument> applicationDocuments;
}
Table 2
@Entity
@Table(name = "applicationDocuments")
public class ApplicationDocument {
@Id
@GeneratedValue(strategy = GenerationType.AUTO)
@Column(name = "id", nullable = false)
private Long id;
@ManyToOne()
@JoinColumn(name = "applicationid")
@JsonBackReference
@Audited
private Application application;
@Audited
private String file;
}
This will create two audit tables, and the data is revisioned every time after insert, update and delete. Works fine till here
But to retrieve revisions
I have a ApplicationRepository which extends springs "RevisionRepository"
So when I fetch something like applicationRepository.getRevisions({{myApplicationId}}). Then when I look at revision entities returned, the one to many relation is always returned as null.
I would expect it to return a list with whatever ApplicationDocuments existed during that revision time.
Any ideas what am I missing here
The problem here is in the mapping for Application.
While both entities are being audited by Envers because they contain at least one @Audited non-id attribute, the inverse side of the collection in Application is not being audited. In short, Envers ignores the attribute because @AuditJoinTable by itself doesn't trigger the attribute to be included in the audit metadata.
You need to change your Application entity so that the collection is mapped as follows
@OneToMany(mappedBy = "application")
@Audited
@AuditJoinTable
private List<ApplicationDocument> applicationDocuments;
A shortcut to remember is that if all attributes of an entity are to be audited by Envers, you can instead annotate the actual class with @Audited to minimize the verbosity if that helps and you would have avoided having this problem too :).