activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Raul Kripalani <r...@evosent.com>
Subject Upgrading only AMQ broker in OSGi container with Camel
Date Fri, 29 Nov 2013 00:56:19 GMT
Hello guys,

When installing AMQ 5.9.0 on Karaf, it seems that all AMQ packages are now
contained in a single activemq-osgi bundle, including the Camel component.

[ 477] [Active     ] [Created     ] [       ] [   50] activemq-osgi (5.9.0)
> exports 477 | grep camel
   477 org.apache.activemq.camel.component.broker; version=5.9.0
   477 org.apache.activemq.camel; version=5.9.0
   477 org.apache.activemq.camel.converter; version=5.9.0
   477 org.apache.activemq.camel.component; version=5.9.0

Why did AMQ shift away from the modularized architecture that cleanly
separated AMQ and Camel elements?

As a consequence, it's now impossible to upgrade only AMQ, because doing so
drags along an updated Camel component which may rely on Camel APIs which
were introduced later. In fact, this is the case when upgrading from AMQ
5.8.0 => 5.9.0 within an environment with Camel 2.10. Note this exception:

Caused by: java.lang.ClassNotFoundException:
org.apache.camel.spi.EndpointCompleter not found by
org.apache.camel.camel-core [130]


Am I overlooking something?

Moreover, it seems that installing the activemq-client feature ends up
installing the activemq-osgi bundle which, once again, contains all broker
packages. What happened to the OSGi spirit? ;-)

Regards,

*Raúl Kripalani*
Apache Camel PMC Member & Committer | Enterprise Architect, Open Source
Integration specialist
http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
http://blog.raulkr.net | twitter: @raulvk

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message