Sure, it's rev 19928: I register both a TX synchronization and a before
completion process. So:
* for a JTA environment, part of the audit records will be written in the
before completion process (if there was a manual flush), and part in the tx
sync (automatic flush). Both propagate exceptions
A, Hibernate Search has the same problem but I could not pin point the
issue.
Can you point me to the temp patch approach you're using.
On 10 juil. 2010, at 10:05, Adam Warski wrote:
> Hello,
>
> because the thread is a bit old a small reminder what it was about:
> Envers used TX Synchroniz
