You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Christian Schneider (JIRA)" <ji...@apache.org> on 2017/05/29 16:03:04 UTC
[jira] [Updated] (ARIES-1690) Ignored rollbackOn element of
Transactional annotation
[ https://issues.apache.org/jira/browse/ARIES-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christian Schneider updated ARIES-1690:
---------------------------------------
Affects Version/s: transaction-blueprint-2.1.0
Fix Version/s: transaction-blueprint-2.2.0
> Ignored rollbackOn element of Transactional annotation
> ------------------------------------------------------
>
> Key: ARIES-1690
> URL: https://issues.apache.org/jira/browse/ARIES-1690
> Project: Aries
> Issue Type: Bug
> Components: Transaction
> Affects Versions: transaction-blueprint-2.1.0
> Reporter: Kevin Vanbockryck
> Assignee: Christian Schneider
> Fix For: transaction-blueprint-2.2.0
>
>
> Here is a simple example-method, when I use this the document ends up in the database.
> @Transactional(value = Transactional.TxType.REQUIRED
> ,rollbackOn = {Exception.class}
> )
> public void store(Document document) throws Exception {
> entityManager.persist(document);
> throw new Exception();
> }
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)