aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Schneider (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (ARIES-1364) transaction.manager causes cascading refreshs in karaf 4
Date Mon, 03 Aug 2015 14:46:04 GMT

    [ https://issues.apache.org/jira/browse/ARIES-1364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14651920#comment-14651920
] 

Christian Schneider edited comment on ARIES-1364 at 8/3/15 2:45 PM:
--------------------------------------------------------------------

Why do you think the transaction API should be in transaction.manager?
About my commit. I just removed the Export-Package statements. This causes the maven bundle
plugin to not embed the api anymore.
Btw. The spring case is not the only case where transaction.manager is being refreshed. We
also had this issue when it was rewired to an external version of the jta API which some features
bring.
Another reason to make the API external is that karaf 4 now also allows to deploy the jta
1.2 API. So as there are two API version choices I think it is better to no embed one of them.


was (Author: chris@die-schneider.net):
Why do you think the transaction API should be in transaction.manager?
About my commit. I just removed the Export-Package statements. This causes the maven bundle
plugin to not embed the api anymore.
Btw. The spring case is not the only case where transaction.manager is being refreshed. We
also had this issue when it was rewired to an external version of the jta API which some features
bring.

> transaction.manager causes cascading refreshs in karaf 4
> --------------------------------------------------------
>
>                 Key: ARIES-1364
>                 URL: https://issues.apache.org/jira/browse/ARIES-1364
>             Project: Aries
>          Issue Type: Bug
>          Components: Transaction
>    Affects Versions: transaction-manager-1.1.1
>            Reporter: Christian Schneider
>            Assignee: Christian Schneider
>             Fix For: transaction-manager-1.3.0
>
>
> transaction.manager embeds the transaction api. So all bundles that use the transactions
api are wired to it.
> Unfortunately it also has optional imports like for the spring transactions. So if such
an optional import is loaded then all bundles using transactions are also reloaded. 
> The simple solution is to not embed the transaction api and instead install it spearately.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message