[
https://issues.apache.org/jira/browse/CAMEL-20600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17847516#comment-17847516
]
Raymond commented on CAMEL-20600:
---------------------------------
Yes, I guess you are right. In Assimbly I support both brokers through one API.
It's then possible to use both classic and artemis standalone or embedded in
the Camel runtime (which makes it possible to skip network traffic and use
broker vm).
For now, I think around 95% > will use ActiveMQ 5 for a while. The adoption of
Java 17 and 21 is going relatively fast though, so this may switch quickly in
the future. Therefore, one could also make an ActiveMQ5 component, while
setting the default component to 6 (based on adoption).
Unfortunately, not a lot of time myself to make a proper component for the
project. For now, I used the generic JMS component and set a
pooledconnectionfactory manually with the ActiveMQ 6 libraries.
> camel-activemq - Upgrade to ActiveMQ classic 6.x or create camel-activemq6
> --------------------------------------------------------------------------
>
> Key: CAMEL-20600
> URL: https://issues.apache.org/jira/browse/CAMEL-20600
> Project: Camel
> Issue Type: Dependency upgrade
> Components: camel-activemq
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Major
> Fix For: 4.7.0
>
>
> We test with 5.18.x which is widely in use.
> The newer 6.x is JDK17 and jakarta ee compatible.
> We may consider having camel-activemq6 as a component for the newer
> client/broker. So we can keep the older around for the many 5.x users.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
