[hibernate-issues] [Hibernate-JIRA] Updated: (HHH-6164) Prefer regsitering JTA syncs via TransactionManager

[Steve Ebersole (JIRA)]

     [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-6164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steve Ebersole updated HHH-6164:
--------------------------------

    Summary: Prefer regsitering JTA syncs via TransactionManager  (was: We really need to prefer regsitering JTA syncs via TransactionManager)

> Prefer regsitering JTA syncs via TransactionManager
> ---------------------------------------------------
>
>                 Key: HHH-6164
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6164
>             Project: Hibernate Core
>          Issue Type: Bug
>          Components: envers
>    Affects Versions: 4.0.0.Alpha2
>            Reporter: Steve Ebersole
>            Assignee: Steve Ebersole
>             Fix For: 4.0.0.Alpha3
>
>
> Apparently there is an implication to using {{TransactionSynchronizationRegistry}} with regards to the order the regsitered {{Synchronization}}s get called in relation to {{Synchronization}}s registered directly with the {{TransactionManager}}.  This is specifically causing problems in initial attempts to integrate 4.0 into JBoss AS 7.0 for example.  Not sure who/what is at fault, but regsitering our {{Synchronization}} directly with the {{TransactionManager}} fixes the problems. 

-- 
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.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira