aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Charlie Mordant (JIRA)" <>
Subject [jira] [Commented] (ARIES-1364) transaction.manager causes cascading refreshs in karaf 4
Date Mon, 03 Aug 2015 14:50:04 GMT


Charlie Mordant commented on ARIES-1364:

I'm totally with your idea Christian: Aries JTA refresh is really hard to tackle in K4 (the
same for K304).
Also Aries-JTA is not an API but an implementation so it's a really good pattern to decouple
spec from impl

> transaction.manager causes cascading refreshs in karaf 4
> --------------------------------------------------------
>                 Key: ARIES-1364
>                 URL:
>             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

View raw message