Envers 1.2.1.GA

Envers is a library that aims to enable easy versioning of persistent JPA classes. All that you have to do is annotate your persistent class or some of its properties, that you want to version, with @Versioned. For each versioned 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.<br /><br />Similarly to Subversion, the library has a concept of revisions. Basically, one transaction commit is one revision (unless the transaction didn't modify any versioned 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.<br /><br />The library works with Hibernate and Hibernate Entity Manager (see hibernate.org). For the versioning 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.<br /><br />In the future, the library will support versioning of arbitrary relationships. It will also include support for "revisioning groups", which will de-centralize the revisions table, if there are independend groups of entities versioned. Another important space-saving feature will be the possibility to store only diffs between revisions, not whole properties (this of course applies only to strings and byte arrays).<br /><br />Here are some key features of "Envers":<br /><br />?*A* versioning of basic properties (strings, integers, longs...)<br />?*A* versioning of embedded components, which are composed of basic properties<br />?*A* versioning of classes with simple, composite and embedded ids<br />?*A* versioning of one-to-one uni- (only on the owning side) and bi-directional relations<br />?*A* versioning of one-to-many uni- (only on the owning side) and bi-directional relations<br />?*A* support for secondary tables<br />?*A* logging data for each revision using a "revision entity"<br />?*A* querying historical data

Requirements:	No special requirements
Platforms:	*nix, Linux
Keyword:	Basic,  Bidirectional,  Embedded,  Entities,  Envers,  Hibernate,  Historical,  Library,  Owning,  Properties,  Query,  Revision,  Revisions,  Strings,  Support,  Transaction,  Versioned,  Versioning,  Works
Users rating:	0/10