[
https://issues.apache.org/jira/browse/AMQ-7309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17552213#comment-17552213
]
Robbie Gemmell commented on AMQ-7309:
-------------------------------------
JBs response was simply incorrect for what you asked given you had mentioned
Jakarta EE 9, which used the 3.0 spec that moved the API into the jakarta.jms
package namespace. His answer is relevant only to the Jakarta EE 8 case where
its 2.0[.x] API spec still used the earlier javax.jms package namespace, and
could be used with the ActiveMQ 5.x impl (so long as you dont call any of the
JMS 2 methods). ActiveMQ 5 releases cant use the Jakarta Messaging 3.0 / 3.1
API as the namespaces differ (once this Jira is done the codebase could perhaps
also be updated to support the new API namepace).
Aside: ActiveMQ Artemis has had EE9 / Jakarta Messaging 3.0 support for some
time, e.g see artemis-jakarta-client, and is being updated to the
almost-unchanged EE10 / 3.1 spec in the coming 2.23.0 release that is
currently under vote.
{quote}I didn't write it in my previous comment but my intention is to move
from Java11 towards 17. As you probably are well aware, this means that the
javax.jms package is evicted from the JDK.
{quote}
The spec wasnt part of the JDK so its still quite possible to use javax.jms on
JDK17. You may seperately have other dependencies that do actually require
using the new spec package however.
> Add JMS 2.0 API support
> -----------------------
>
> Key: AMQ-7309
> URL: https://issues.apache.org/jira/browse/AMQ-7309
> Project: ActiveMQ
> Issue Type: New Feature
> Components: Broker, JMS client
> Reporter: Jean-Baptiste Onofré
> Assignee: Jean-Baptiste Onofré
> Priority: Major
> Labels: #jms2
> Fix For: 5.18.0
>
> Time Spent: 17h 20m
> Remaining Estimate: 0h
>
> * API-only inclusion
> * JMS 2.0 objects throw UnsupportedOperationException
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
