[
https://issues.apache.org/jira/browse/AMQ-9297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17751985#comment-17751985
]
Robbie Gemmell edited comment on AMQ-9297 at 8/8/23 10:05 AM:
--------------------------------------------------------------
As explained on the [users list
thread|https://lists.apache.org/thread/yvqmftv5nv975h9h8lwvwm4wowb8mhdo] the
5.18.x zip distribution is still entirely javax.jms API package based, so this
is expected. Only the separate transitional activemq-client-jakarta module is
jakarta.jms API package based.
For more, see
[https://lists.apache.org/thread/yvqmftv5nv975h9h8lwvwm4wowb8mhdo],
[https://activemq.apache.org/jms2], AMQ-9239,
[https://github.com/apache/activemq/pull/996]
was (Author: gemmellr):
As explained on the (users list
thread)[https://lists.apache.org/thread/yvqmftv5nv975h9h8lwvwm4wowb8mhdo] the
5.18.x zip distribution is still entirely javax.jms API package based, so this
is expected. Only the separate transitional activemq-client-jakarta module is
jakarta.jms API package based.
For more, see
[https://lists.apache.org/thread/yvqmftv5nv975h9h8lwvwm4wowb8mhdo],
[https://activemq.apache.org/jms2], AMQ-9239,
[https://github.com/apache/activemq/pull/996]
> Activemq jakarta namespace support still depends on some javax.jms packages
> ---------------------------------------------------------------------------
>
> Key: AMQ-9297
> URL: https://issues.apache.org/jira/browse/AMQ-9297
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.18.2
> Reporter: Jayeshkumar
> Priority: Major
>
> Hello,
> I am currently moving from 5.16.5 version to activemq 5.18.2 which has
> support for jakarta namespace, however there are still references to old
> javax packages, I am getting ClassNotFoundException for
> javax.jms.JMSException, but the right package should be jakarta.jms which is
> already present
> In the 5.18.2 zip distribution, I see jakarta-jms-api-2.X is used for which
> the underlying package is still javax and not jakarta. Rather to fully
> support jakarta namespace, we should plan and move to jakarta-jms-3.X which
> has the right package structure. Any reference to javax.jms should be
> replaced to use the new namespace
> So the existing support needs some more work before we can use it seamlessly.
> Can you please review and share your views on this
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
