[hibernate-issues] [Hibernate-JIRA] Resolved: (HHH-7296) NPE in JtaTransaction#markRollbackOnly

[Steve Ebersole (JIRA)]

     [ https://hibernate.onjira.com/browse/HHH-7296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steve Ebersole resolved HHH-7296.
---------------------------------

    Resolution: Fixed

> NPE in JtaTransaction#markRollbackOnly
> --------------------------------------
>
>                 Key: HHH-7296
>                 URL: https://hibernate.onjira.com/browse/HHH-7296
>             Project: Hibernate ORM
>          Issue Type: Bug
>          Components: core
>            Reporter: Steve Ebersole
>            Assignee: Steve Ebersole
>             Fix For: 4.1.3
>
>          Time Spent: 10m
>
> Mainly this comes up in usage within Spring with Spring-managed transactions.  The problem being that transactions are really "container managed", just in a Spring-specific way.  Spring managed transactions to not expose access to TM, so Hibernate users in Spring are forced to use JtaTransactionFactory but the HIbernate transaction API is not used control the transactions, so if calls come into JtaTransaction#markRollbackOnly under these circumstances the userTransaction instance state is null (since #begin was never called). 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira