In our project we use envers to keep historical data for our entities. The historical data has a business value. As we know, the auditing occurs at the before completion phase, where exceptions are caught and not propagated.
The scenario is the following: imagine the entity change was successfully persisted but somehow, during the revision creation in the database, we get any sort of for example jdbc exception. What we noticed is that the entity was changed in the database without a revision created, causing a data inconsistency.
Is there any way with envers to have the whole transaction rollback due to failures during revision creation?