[
https://issues.apache.org/jira/browse/AMQ-7309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17348588#comment-17348588
]
Christopher L. Shannon commented on AMQ-7309:
---------------------------------------------
[~romain.manni-bucau], There is no agreement, Tim Bish also echoed my concerns.
I'm not saying no to JMS 2.0 or having a gradual implementation that is done in
pieces. All of that is fine.
The part I'm disagreeing with is having the new methods call the old 1.1
methods and I'm not going to change my mind on that point. That is a hard -1
from me and is a non starter.
As JB said, something like throwing OperationNotSupportedException makes sense
because guess what? It's not supported. It would be ridiculous to just delegate
to the other methods with no indication as it's completely different semantics.
> Add JMS 2.0 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
> Fix For: 5.17.0
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
