[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-5315) AuditJoinTable rows are no longer flushed to the database

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-5315?page=c... ] Erik-Berndt Scheper commented on HHH-5315: ------------------------------------------ Well, I've tried to reproduce this using the Envers test suite, but failed (until now). I have a few ideas why this might be the case. One suspect is the behaviour of the transaction manager in the test suite (in the sense that its behavious is different from an XA enabled JTA transaction manager). Does that make sense? Another suspect is that I'm using JPA with a Spring persistence context. Perhaps Envers is using the actionqueue in a way that was never intended? I worked around the issue by adding an extra Spring AOP interceptor before the spring tx interceptor. This extra inceptor does an extra flush and then everything works fine. Another thing I tried was to add an extra transaction synchronization and add the flush there, but to my surprise that did not work. Anyway, I did succeed to reproduce this in an Eclipse project with a couple of open source third party libraries. I could add that project to this issue with some extra info if this helps. Note: this issue also affects 3.5.3 and current trunk (3.6.0-snapshot). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira