karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Felix Wassmer (JIRA)" <j...@apache.org>
Subject [jira] [Created] (KARAF-4122) Custom interceptor prohibits declarative transactions
Date Wed, 18 Nov 2015 14:17:10 GMT
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:

This message was sent by Atlassian JIRA

View raw message