I'm trying to use Envers with a JPA persistence unit without JTA transaction scope.
I've created a new RevisionEntity with the correspondent RevisionListener. When I was testing this implementation I noticed that when a exception occurs in my RevisionListener, the transaction is not all rollbacked, that is, the "operational" data is committed, but the audit data is not.
Is this an expected behavior? Shouldn't the transaction be all rollbacked?
I'm using Hibernate 3.3.1 and Envers 1.2.0.GA, with hibernate.transaction.factory_class property set to org.hibernate.transaction.JDBCTransactionFactory.
The transaction should be rolled back of course. As far as I remember it rolls back in my setting, but that surely needs an intergration test :) Can you create a JIRA bug?