[
https://issues.apache.org/jira/browse/ARIES-1800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16467068#comment-16467068
]
Christian Schneider commented on ARIES-1800:
--------------------------------------------
I did not find anything about class level vs method level in the spec.
Personally I would prefer override behaviour. Event that has to be defined
clearly though. For example one could argue that a method level Annotation
completely overrides the class level annotation even if it does not define
rollbackOn or dontRollbackOn. The alternative is that we only override the
behaviour of each attribute if it is specified.
I will try to get someone involved in the specs to give us some feedback.
> 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)
