activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dejan Bosanac (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (AMQ-4909) OSGi granularity of activemq-osgi bundle
Date Wed, 11 Dec 2013 15:43:08 GMT

     [ https://issues.apache.org/jira/browse/AMQ-4909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Dejan Bosanac reassigned AMQ-4909:
----------------------------------

    Assignee: Dejan Bosanac  (was: Jean-Baptiste Onofré)

> OSGi granularity of activemq-osgi bundle
> ----------------------------------------
>
>                 Key: AMQ-4909
>                 URL: https://issues.apache.org/jira/browse/AMQ-4909
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: OSGi/Karaf
>    Affects Versions: 5.9.0
>            Reporter: Raul Kripalani
>            Assignee: Dejan Bosanac
>
> Installing any AMQ feature, whether activemq-client, activemq-broker or activemq-camel,
ends up installing the activemq-osgi bundle which is a one-stop-shop include-all bundle for
AMQ.
> In other words, if you install activemq-client you end up with a fully fledged broker.
If you install activemq-camel, you also end up with a fully fledged broker.
> Moreover, the AMQ Camel component is part of the activemq-osgi bundle, which means that
you can no longer upgrade only the AMQ broker if you're running in a setup with Camel, because
it drags along an updated Camel AMQ component which may require newer Camel APIs. 
> At least it's not possible via Karaf features. A workaround may be to fall back to installing
individual AMQ bundles.
> More info here: http://activemq.2283324.n4.nabble.com/Upgrading-only-AMQ-broker-in-OSGi-container-with-Camel-tp4674930.html.



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)

Mime
View raw message