karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KARAF-4624) Create Karaf component to create Activemq connection factories
Date Thu, 04 Aug 2016 12:14:20 GMT

    [ https://issues.apache.org/jira/browse/KARAF-4624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15407637#comment-15407637

ASF subversion and git services commented on KARAF-4624:

Commit 3e6a6ff5f546b41812d103a4e39efd4075b682dc in karaf's branch refs/heads/karaf-4.0.x from
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=3e6a6ff ]

[KARAF-4624] Remove module again as it is now at ActiveMQ

> Create Karaf component to create Activemq connection factories
> --------------------------------------------------------------
>                 Key: KARAF-4624
>                 URL: https://issues.apache.org/jira/browse/KARAF-4624
>             Project: Karaf
>          Issue Type: New Feature
>    Affects Versions: 4.0.5
>            Reporter: Christian Schneider
>            Assignee: Christian Schneider
>             Fix For: 4.1.0, 4.0.6
> We already have the jms feature which allows to create connection factories as services.
The connection factories are created as blueprint.xmls and put into the deploy folder.
> For many cases this is good enough but it has some drawbacks:
> - Since karaf 4 we do not require blueprint anymore. So if someone does not want to use
blueprint he still has to use it just for the connection factories
> - The deploy folder often has timing issues
> As ActiveMQ is the most used jms server in the karaf environment I propose to create
a small bundle for it that creates connection factory services from configs. 
> This will make it easier for people to have a non blueprint deployment and also not rely
on the deploy folder.

This message was sent by Atlassian JIRA

View raw message