Support short-naming of audit strategies via configuration.

Description

Currently only a FQN class name can be specified for audit strategies in configuration. It would be useful moving forward to introduce short-namings as an alternative that are more resilient to internal code refactoring across releases and that don't impose a configuration change on users when doing so.

For example, rather than a user configuring:

We'd prefer to use:

As an example to work from Hikari registers 2 short names for its connection pool, see:

Environment

None

Activity

Show:
Chris Cranford
December 5, 2017, 4:07 PM

Users will be able to specify the following short-names to be mapped to their equivalent strategies:

Short Name

Strategy Class

<no value specified>

org.hibernate.envers.strategy.DefaultAuditStrategy

default

org.hibernate.envers.strategy.DefaultAuditStrategy

DefaultAuditStrategy

org.hibernate.envers.strategy.DefaultAuditStrategy

org.hibernate.envers.strategy.DefaultAuditStrategy

org.hibernate.envers.strategy.DefaultAuditStrategy

validity

org.hibernate.envers.strategy.ValidityAuditStrategy

ValidityAuditStrategy

org.hibernate.envers.strategy.ValidityAuditStrategy

org.hibernate.envers.strategy.ValidityAuditStrategy

org.hibernate.envers.strategy.ValidityAuditStrategy

This will allow backward compatibility as well as support for the newer short-naming convention.

Steve Ebersole
December 6, 2018, 3:43 PM

Preparing Alpha1 release

Assignee

Chris Cranford

Reporter

Chris Cranford

Fix versions

Labels

None

backPortable

None

Suitable for new contributors

None

Requires Release Note

Affirmative

Pull Request

None

backportDecision

None

Components

Priority

Major
Configure