You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tomee.apache.org by "Svetlin Zarev (JIRA)" <ji...@apache.org> on 2017/06/02 09:32:04 UTC

[jira] [Updated] (TOMEE-2049) JTA 1.2 compliance: The combination of @Transactional.dontRollbackOn=XXX,rollbackOn=XXX is not respected

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

Svetlin Zarev updated TOMEE-2049:
---------------------------------
    Summary: JTA 1.2 compliance: The combination of  @Transactional.dontRollbackOn=XXX,rollbackOn=XXX  is not respected  (was: JTA 1.2 compliance:The combination of  @Transactional.dontRollbackOn=XXX,rollbackOn=XXX  is not respected)

> 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
>
> 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)