activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Richard Kettelerij (JIRA)" <>
Subject [jira] [Commented] (AMQ-4909) OSGi granularity of activemq-osgi bundle
Date Thu, 12 Dec 2013 09:18:07 GMT


Richard Kettelerij commented on AMQ-4909:

This is definitely a step in the right direction, thanks []!

Although I don't think the issue is entirely resolved. The activemq-camel feature still depends
on the activemq-client feature which IMHO is too heavyweight. This is primarily due to the
large/uber activemq-osgi bundle included in the activemq-client feature.

> OSGi granularity of activemq-osgi bundle
> ----------------------------------------
>                 Key: AMQ-4909
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: OSGi/Karaf
>    Affects Versions: 5.9.0
>            Reporter: Raul Kripalani
>            Assignee: Dejan Bosanac
>             Fix For: 5.10.0
> 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
> 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:

This message was sent by Atlassian JIRA

View raw message