[
https://issues.apache.org/jira/browse/AMQ-5736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16593091#comment-16593091
]
Adrian Cole commented on AMQ-5736:
----------------------------------
I'd like to make a comment on this. Artemis is cool, but activemq-broker is
very light and its classpath doesn't depend on netty for example. I was hoping
to test JMS using something that doesn't require netty, that's the only reason
I was hoping for 2.0 capability. It should be possible to support both versions
by overloading but not adding the Override qualifier to the source implementing
2.0 methods. This is just a suggestion as really the "vm" transport is fast
lovely, flake free, and doesn't have as many conflicty deps.
> JMS 2.0 Support
> ---------------
>
> Key: AMQ-5736
> URL: https://issues.apache.org/jira/browse/AMQ-5736
> Project: ActiveMQ
> Issue Type: New Feature
> Components: Broker
> Affects Versions: 5.11.1
> Reporter: Matt Pavlovich
> Priority: Major
>
> Expand broker support to include JMS 2.0.
> The biggest impacts are going to be the client side changes to support the
> simplified API (It looks like AMQ-5383 covers that), and the ability to share
> subscriptions across multiple clients.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
