[
https://issues.apache.org/jira/browse/AMQ-7309?focusedWorklogId=628595&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-628595
]
ASF GitHub Bot logged work on AMQ-7309:
---------------------------------------
Author: ASF GitHub Bot
Created on: 27/Jul/21 16:40
Start Date: 27/Jul/21 16:40
Worklog Time Spent: 10m
Work Description: mattrpav commented on pull request #682:
URL: https://github.com/apache/activemq/pull/682#issuecomment-887664563
> Note that by specifically adding an implementation of setJMSDeliveryTime
that throws UOE, this change will likely actually break sending of ActiveMQ 5.x
messages through other existing JMS 2 providers that handle being given JMS 1.x
message objects not implementing the method, as they wont handle it being
implemented but deliberately throwing UOE. Unlike the session etc they cant
check any version metadata first to avoid the method as all they see is the
message.
@gemmellr That is an extreme edge use case-- one that is acceptable for a RC
release. These JMS 2.0 methods won't be unimplemented for long. Feel free to
add a documentation note if you know of some users that have this scenario and
would be impacted.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 628595)
Time Spent: 3h 40m (was: 3.5h)
> 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
>
> Time Spent: 3h 40m
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
