From Hibernate 3.5, Envers is included as a Hibernate core module.
For downloads, please go to the Hibernate downloads page. Envers is also available in JBoss Maven repositories.
Documentation is hosted on the Hibernate docs site.
This page won't be updated in the future. All new releases, documentation updates etc. will be done through the Hibernate site.
You can track Envers updates via the Envers blog.
Envers: Easy Entity Auditing
@Audited. For each audited entity, a table will be created, which will hold the history of changes made to the entity. You can then retrieve and query historical data without much effort.
Similarly to Subversion, Envers has a concept of revisions. Basically, one transaction is one revision (unless the transaction didn't modify any audited entities). As the revisions are global, having a revision number, you can query for various entities at that revision, retrieving a (partial) view of the database at that revision. You can find a revision number having a date, and the other way round, you can get the date at which a revision was commited.
Envers is a Hibernate core module and works with Hibernate and Hibernate Entity Manager (see hibernate.org). For the auditing to work properly, the entities must have immutable unique identifiers (primary keys). You can use Envers wherever Hibernate works: standalone, inside JBoss AS, with JBoss Seam or Spring.
Some of the features:
- auditing of all mappings defined by the JPA specification
- auditing of some Hibernate mappings, which extend JPA, like custom types and collections/maps of "simple" types (Strings, Integers, etc.) (see here for one exception)
- logging data for each revision using a "revision entity"
- querying historical data
For a quick tutorial on how to use Envers, see the Quick Start page.
You can also try a console demo, which is a simple app where you can create, modify and view versions of two simple entities (
Address), and modify a one-to-many relation between them. By default it uses hsqldb, but you can overwrite the
persistence.xml and check how it works with your database, see the structure of the generated tables etc.
Blog of Adam WarskiJava, Scala, programming, ...
- Big data: when single node is better than clustered
- Mar 6, 2014 8:22 AM by Adam Warski
- Using Scala traits as modules, or the “Thin Cake” Pattern
- Feb 25, 2014 8:07 AM by Adam Warski
- Using JavaCV with Scala and SBT
- Jan 24, 2014 10:40 AM by Adam Warski
- How do iBeacons work?
- Jan 13, 2014 3:34 PM by Adam Warski
- Traffic simulation game in Elm
- Jan 7, 2014 7:08 AM by Adam Warski