[
https://issues.apache.org/jira/browse/ARIES-1364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14651915#comment-14651915
]
David Jencks commented on ARIES-1364:
-------------------------------------
I haven't been able to figure out what you did from jira, but I'm pretty
strongly -1 on removing the api from transaction manager. Have you considered
using both optional and dynamic imports for the spring packages?
> 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)
