Hi I just realized and digged a bit into the spring-jms, and noticed its adaptive to whether you have JMS 1.1 or 2.0 APIs on the classpath.
https://github.com/spring-projects/spring-framework/blob/master/spring-jms/src/main/java/org/springframework/jms/listener/AbstractMessageListenerContainer.java So in essence we could have camel-jms support both of them at the same time. For OSGi then camel-jms has already been opened up to bind to both 1.1 and 2.0 APIs <camel.osgi.import.additional>javax.jms;version="[1.1,3)"</camel.osgi.import.additional> So we could likely just move the new options I added to camel-jms2 to camel-jms so we only have one component that supports both 1.1 and 2.0 OOTB. The new options are default false, and therefore if you use a JMS 1.1 client then it should not affect that as camel-jms does not trigger spring-jms to use JMS 2.0 APIs. On Thu, Sep 14, 2017 at 3:39 PM, Claus Ibsen <claus.ib...@gmail.com> wrote: > Hi > > Just wanted to share we have a new component in the works for a > camel-jms2 component that uses the JMS 2.0 API so you can use shared > (durable) topics. The component extends the existing camel-jms > component which is based on JMS 1.1 api. > > I pushed my work on the jms2 branch so anyone can take a look and > provide feedback. > > To use the new functionality of JMS 2.0 you need a JMS 2.0 broker such > as Apache Artemis. The classic ActiveMQ 5.x is JMS 1.1 only. > > https://github.com/apache/camel/tree/jms2 > > Feedback is welcome before we merge this to the master branch for > inclusion in the upcoming Camel 2.20 release. > > > -- > Claus Ibsen > ----------------- > http://davsclaus.com @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 -- Claus Ibsen ----------------- http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
