tomee-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Romain Manni-Bucau (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (TOMEE-2049) JTA 1.2 compliance: The combination of @Transactional.dontRollbackOn=XXX,rollbackOn=XXX is not respected
Date Fri, 02 Jun 2017 09:40:05 GMT

     [ https://issues.apache.org/jira/browse/TOMEE-2049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Romain Manni-Bucau resolved TOMEE-2049.
---------------------------------------
       Resolution: Fixed
         Assignee: Romain Manni-Bucau
    Fix Version/s: 7.0.4

> JTA 1.2 compliance: The combination of  @Transactional.dontRollbackOn=XXX,rollbackOn=XXX
 is not respected
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: TOMEE-2049
>                 URL: https://issues.apache.org/jira/browse/TOMEE-2049
>             Project: TomEE
>          Issue Type: Bug
>            Reporter: Svetlin Zarev
>            Assignee: Romain Manni-Bucau
>             Fix For: 7.0.4
>
>
> Imagine you have a cdi bean method annotated with 
> {code}
> @Transactional(rollbackOn={RollBackException.class}, dontRollbackOn={RollBackException.class})
> {code}
> According to the JTA 1.2 spec, section 3.7, the transaction must not be marked for roll
back:
> {code}
> The following will cause the transaction to be marked for rollback for all runtime exceptions
and all SQLException types except for SQLWarning.
> @Transactional(rollbackOn={SQLException.class},
> dontRollbackOn={SQLWarning.class})
> {code}
> Yet TomEE marks the transaction for roll back.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message