[
https://issues.apache.org/jira/browse/AMQ-7309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17552618#comment-17552618
]
Robbie Gemmell commented on AMQ-7309:
-------------------------------------
{quote}I tried moving to the Artemis client but unfortunately it can't connect
to Amazon MQ through the OpenWire protocol. AMQ runs the ActiveMQ 5 engine.
{quote}
Right, I wasnt suggesting you would be able to use only the client, but simply
directing you to where the Jakarta client is as its a separate artifact from
the long standing artemis-jms-client. The Artemis clients use the Artemis Core
protocol, so cant connect to the 5.x broker as that doesnt support the Core
protocol (whereas in reverse the 5.x OpenWire client can connect to Artemis).
Currently probably the only jakarta.jms capable client that can connect to 5.x
at all is the Qpid JMS 2.0.0 client using AMQP.
{quote}
You're suggesting I could stay at EE7/8 while moving to OpenJDK17?{quote}
Yes. I'm saying that the two things are not inherently related at all, unless
you do/use something that makes them in some way. Components using the
javax.jms packaged spec can work on JDK17 just fine.
> 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)
