Mailing-List: contact issues-help@karaf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@karaf.apache.org
Date: Thu, 14 Jul 2016 15:58:20 +0000 (UTC)
From: "Christian Schneider (JIRA)" <jira@apache.org>
To: issues@karaf.apache.org
Message-ID: <JIRA.12989498.1468511877000.29478.1468511900562@Atlassian.JIRA>
In-Reply-To: <JIRA.12989498.1468511877000@Atlassian.JIRA>
References: <JIRA.12989498.1468511877000@Atlassian.JIRA> <JIRA.12989498.1468511877402@arcas>
Subject: [jira] [Created] (KARAF-4624) Create Karaf component to create
 Activemq connection factories
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 14 Jul 2016 15:58:22 -0000

Christian Schneider created KARAF-4624:
------------------------------------------

             Summary: 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
(v6.3.4#6332)