You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Felix Wassmer (JIRA)" <ji...@apache.org> on 2015/11/18 15:17:10 UTC
[jira] [Created] (KARAF-4122) Custom interceptor prohibits
declarative transactions
Felix Wassmer created KARAF-4122:
------------------------------------
Summary: Custom interceptor prohibits declarative transactions
Key: KARAF-4122
URL: https://issues.apache.org/jira/browse/KARAF-4122
Project: Karaf
Issue Type: Bug
Affects Versions: 4.0.3
Environment: Karaf 4.0.2 + 4.0.3, Windows 7 x64, Oracle jdk 1.8
Reporter: Felix Wassmer
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)