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

Raul Kripalani updated AMQ-4909:
--------------------------------

    Description: 
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.

  was:
Installing any AMQ feature, whether activemq-client, activemq-broker or 
activemq-camel, ends up installing the activemq-osgi bundle which is a one-stop 
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.


> 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: Jean-Baptiste Onofré
>
> 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#6144)

Reply via email to