ActiveMQ Artemis fully implements the JMS specification so any client using JMS (e.g. Apache Camel) should work without issues. For what it's worth, Artemis ships with an example [1] using Apache Camel for bridging messages between a 5.x broker instance and an Artemis instance.
The ActiveMQ 5.x has a lot of features, some of which are commonly used and some of which aren't. The goal isn't 100% feature parity, but feature parity where it makes sense. I believe most of the big use-cases are covered. If you could clarify your particular use case(s) then I could provide a more specific answer. I don't understand what you mean by "durability of Artemis." Can you elaborate on this question? Justin [1] https://github.com/apache/activemq-artemis/tree/master/examples/features/sub-modules/inter-broker-bridge/artemis-jms-bridge#5x-to-artemis-camel-jms-bridge On Mon, Apr 9, 2018 at 12:14 AM, SubashKunjupillai <subas...@ericsson.com> wrote: > Hi Tim, > > Thanks for your suggestions. > > Saying that, moving to ActiveMQ Artemis would be the ideal option. I'm also > not sure whether all the features being used by us (camel routes are used > to > produce and consume JMS messages) with ActiveMQ 5.14.4 will be available in > ActiveMQ Artemis 2.5.0. > > From community perspective can some one comment on the feature > compatibility > and durability of Artemis? > > Regards, > Subash Kunjupillai > > > > ----- > Subash Kunjupillai > -- > Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User- > f2341805.html >
