[
https://issues.apache.org/jira/browse/KARAF-4122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15052388#comment-15052388
]
Christian Schneider commented on KARAF-4122:
--------------------------------------------
[~fwassmer] can you check if the pull request works for you? Btw. I also found
some differences in the NameSpaceHandler. You should only return the xsd path
for known namespace urls and you should return an empty collection for the
managed classes. Not sure if these changes make a difference though.
> 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
> 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)
