[
https://issues.apache.org/jira/browse/AMQ-9295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17751992#comment-17751992
]
Robbie Gemmell commented on AMQ-9295:
-------------------------------------
I believe activemq-jms-pool conversion is already included in the ongoing
Jakarta work for ActiveMQ 5.19.x being done under AMQ-9239 (e.g
https://github.com/apache/activemq/pull/996)
(Aside: Pooled JMS is not simply 'the JMS pool for Artemis', it was
specifically created for enabling usage with other JMS 2 or now Jakarta
Messaging 3 clients)
> activemq-jakarta-pool - A connection pool for Jakarta JMS API
> -------------------------------------------------------------
>
> Key: AMQ-9295
> URL: https://issues.apache.org/jira/browse/AMQ-9295
> Project: ActiveMQ
> Issue Type: New Feature
> Reporter: Claus Ibsen
> Priority: Major
>
> The current activemq-pool is javax JMS based and does not work with Jakarta
> JMS APIs.
> The JMS pool for Artemis can be used instead as it supports Jakarta JMS APIs
> https://github.com/messaginghub/pooled-jms
> And with this factory
> org.messaginghub.pooled.jms.JmsPoolConnectionFactory
> However this and activemq-pool does not offer same features and configuration
> names. So for users that want to use ActiveMQ 5.x but with Jakarta JMS APIs
> then it would be good to do a activemq-jakarta-pool so they can easily
> upgrade and use the same pool as before.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
