[ 
https://issues.apache.org/jira/browse/AMQ-8322?focusedWorklogId=805213&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-805213
 ]

ASF GitHub Bot logged work on AMQ-8322:
---------------------------------------

                Author: ASF GitHub Bot
            Created on: 31/Aug/22 12:43
            Start Date: 31/Aug/22 12:43
    Worklog Time Spent: 10m 
      Work Description: cshannon commented on PR #729:
URL: https://github.com/apache/activemq/pull/729#issuecomment-1232889253

   @gemmellr - Yeah, this could be merged as is and then add a follow on PR for 
getBody, isBodyssignable and JMSConsumer receive body. I think those should be 
implemented for 5.18 as no reason not to really but as you said this PR has 
been open for 9 months so it's time to merge it.
   
   And your comment about the "alpha" thing is what I was getting at with my 
comment about communication to users. Not sure the best way to describe it but 
we need to make it clear this is not fully implemented and kind of a preview or 
alpha/beta of JMS 2.0 changes or however we want to call it.




Issue Time Tracking
-------------------

    Worklog Id:     (was: 805213)
    Time Spent: 17h  (was: 16h 50m)

> 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: 17h
>  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)

Reply via email to