[
https://issues.apache.org/jira/browse/ARIES-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Schneider resolved ARIES-1457.
----------------------------------------
Resolution: Invalid
Assignee: Christian Schneider
See linked karaf issue for details.
> Custom interceptor prohibits declarative transactions
> -----------------------------------------------------
>
> Key: ARIES-1457
> URL: https://issues.apache.org/jira/browse/ARIES-1457
> Project: Aries
> Issue Type: Bug
> Components: Blueprint, Transaction
> Affects Versions: blueprint-core-1.4.5, transaction-blueprint-2.0.0
> Environment: Karaf 4.0.3, Windows 7 x64, Oracle JDK 1.8
> Reporter: Felix Wassmer
> Assignee: Christian Schneider
>
> When using declarative transactions in Karaf 4 (Aries transaction blueprint
> 2.0.0),
> adding a custom interceptor seems to conflict with the aries TxInterceptor.
> Expected behavior
> Interceptor enabled for service A
> Service A with TxType.REQUIRED calls service B with TxType.MANDATORY and
> service B will be executed in a transaction.
> Actual behavior
> Service B throws exception: No transaction present when calling method that
> mandates a transaction.
> (TxInterceptor was not registered for service A and therefore no tx started)
> Disabling the interceptor (removing declaration in blueprint),
> transactional behaviour works as expected (B is executed in a transaction).
> Custom interceptor + tx behavior works as expected when using transaction
> blueprint 1.1.1 and delcaring transactions in blueprint.
> Example to reproduce the issue:
> https://github.com/fwassmer/transaction-chain/
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
