HHH-10688 - Update user guide and migration document regarding envers deprecated settings.
This commit is contained in:
parent
7854e1d338
commit
5331b32a60
|
@ -646,6 +646,12 @@ To use customized Envers event listeners, the following steps are needed:
|
|||
. For the integrator to be automatically used when Hibernate starts up, you will need to add a `META-INF/services/org.hibernate.integrator.spi.Integrator` file to your jar.
|
||||
The file should contain the fully qualified name of the class implementing the interface.
|
||||
|
||||
[NOTE]
|
||||
====
|
||||
The use of `hibernate.listeners.envers.autoRegister` has been deprecated. A new configuration setting
|
||||
`hibernate.envers.autoRegisterListeners` should be used instead.
|
||||
====
|
||||
|
||||
=== Understanding the Envers Schema
|
||||
|
||||
For each audited entity (that is, for each entity containing at least one audited field), an audit table is created.
|
||||
|
|
|
@ -74,3 +74,5 @@ implement JPA methods now in core I decided to implement more of a composition a
|
|||
returns. #getFlushMode has been altered to return JPA's FlushModeType. The Hibernate FlushMode
|
||||
is still available via #getHibernateFlushMode and #setHibernateFlushMode. Same for Session#getFlushMode
|
||||
and EntityManager#getFlushMode.
|
||||
* Setting `hibernate.listeners.envers.autoRegister` has been deprecated in favor of
|
||||
`hibernate.envers.autoRegisterListeners`.
|
||||
|
|
Loading…
Reference in New Issue