[
https://issues.apache.org/jira/browse/AMQ-8322?focusedWorklogId=805205&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-805205
]
ASF GitHub Bot logged work on AMQ-8322:
---------------------------------------
Author: ASF GitHub Bot
Created on: 31/Aug/22 12:16
Start Date: 31/Aug/22 12:16
Worklog Time Spent: 10m
Work Description: gemmellr commented on PR #729:
URL: https://github.com/apache/activemq/pull/729#issuecomment-1232859161
Not implementing the Message getBody and isBodyAssignableTo bits, and also
the JMSConsumer 'recieve body' behaviour when the JMSProducer side 'send
<body>' equivalent _is_ implemented, does seem quite odd. But then to me
personally so does the idea of releasing anything not considered e.g. an alpha,
without so many basic new APIs and most of the core JMS 2 behavioural additions
yet being implemented.
Merging may still make sense, it has been open for 9 months already and it
is after all considered a first-pass...but releasing it isnt really making much
more to me now than it did when 5.17.0 was being prepared 6 months ago; it
hasnt really substantially changed since then. I'll be leaving further review
to others, e.g JB was keen to implement it originally and tends to work on the
5.x releases.
Issue Time Tracking
-------------------
Worklog Id: (was: 805205)
Time Spent: 16h 50m (was: 16h 40m)
> Implement JMS 2.0 Connection createContext methods
> --------------------------------------------------
>
> Key: AMQ-8322
> URL: https://issues.apache.org/jira/browse/AMQ-8322
> Project: ActiveMQ
> Issue Type: New Feature
> Reporter: Matt Pavlovich
> Assignee: Matt Pavlovich
> Priority: Major
> Labels: #jms2
> Fix For: 5.18.0
>
> Time Spent: 16h 50m
> Remaining Estimate: 0h
>
> Add support for JMSContext, JMSProducer and JMSConsumer for working with
> queues
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
