[jboss-jira] [JBoss JIRA] (WFLY-2059) allow Hibernate envers hibernate.listeners.envers.autoRegister == false

[Scott Marlow (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-2059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12804036#comment-12804036 ] 

Scott Marlow commented on WFLY-2059:
------------------------------------

After HHH-8502 is fixed, uncomment "hibernate.listeners.envers.autoRegister=false" in the following source files:

testsuite/integration/basic/src/test/java/org/jboss/as/test/integration/hibernate/SFSBHibernateSessionFactory.java
testsuite/integration/basic/src/test/java/org/jboss/as/test/integration/hibernate/SFSBHibernateTransaction.java
testsuite/integration/basic/src/test/java/org/jboss/as/test/integration/hibernate/SFSBHibernatewithCriteriaSession.java
testsuite/integration/basic/src/test/java/org/jboss/as/test/integration/hibernate/SFSBHibernatewithMetaDataSession.java

                
> allow Hibernate envers hibernate.listeners.envers.autoRegister == false
> -----------------------------------------------------------------------
>
>                 Key: WFLY-2059
>                 URL: https://issues.jboss.org/browse/WFLY-2059
>             Project: WildFly
>          Issue Type: Bug
>          Components: JPA / Hibernate
>            Reporter: Scott Marlow
>            Assignee: Scott Marlow
>             Fix For: 8.0.0.CR1
>
>
> This is a regression in Hibernate 4.3.0.Beta1 that will be fixed by HHH-8501.
> For applications that have Hibernate envers on their classpath and have Hibernate configuration setting hibernate.listeners.envers.autoRegister=false, a NullPointerException is occurring in org.hibernate.envers.event.spi.EnversIntegrator.disintegrate ( http://pastebin.com/BbcgWSeK).
> The workaround is to set hibernate.listeners.envers.autoRegister=true (default setting which allows envers to work with the deployment) or remove envers from their classpath.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira