[jira] [Updated] (ARIES-1800) rollbackOn element of Transactional annotation ignored when set on class level

["Daniel Estermann (JIRA)" <ji...@apache.org>]

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

Daniel Estermann updated ARIES-1800:
------------------------------------
    Description: 
Since ARIES-1690 the methods throwing a checked exception cause a rollback if the related exception is marked for a rollback using rollbackOn element of Transactional annotation set on a method. However this doesn't work for Transactional annotations on the class level.

We also need to clarify how we should handle a exceptions set on both levels class and method. There are at least two options:
* The resulting set of exceptions marked for rollback is an aggregation from both class level and method level annotation.
* Exception set defined on the method level overrides exceptions of the class leve.

  was:
Since ARIES-1690 the methods throwing a checked exception cause a rollback if the related exception is marked for a rollback using rollbackOn element of Transactional annotation set on a method. However this doesn't work for Transactional annotations on the class level.

I would expect a set of exceptions marked for rollback to get aggregated from both class level and method level annotation.


> rollbackOn element of Transactional annotation ignored when set on class level
> ------------------------------------------------------------------------------
>
>                 Key: ARIES-1800
>                 URL: https://issues.apache.org/jira/browse/ARIES-1800
>             Project: Aries
>          Issue Type: Bug
>          Components: Transaction
>    Affects Versions: transaction-blueprint-2.2.0
>            Reporter: Daniel Estermann
>            Priority: Major
>
> Since ARIES-1690 the methods throwing a checked exception cause a rollback if the related exception is marked for a rollback using rollbackOn element of Transactional annotation set on a method. However this doesn't work for Transactional annotations on the class level.
> We also need to clarify how we should handle a exceptions set on both levels class and method. There are at least two options:
> * The resulting set of exceptions marked for rollback is an aggregation from both class level and method level annotation.
> * Exception set defined on the method level overrides exceptions of the class leve.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)