[
https://issues.apache.org/jira/browse/AMQ-8324?focusedWorklogId=947795&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-947795
]
ASF GitHub Bot logged work on AMQ-8324:
---------------------------------------
Author: ASF GitHub Bot
Created on: 11/Dec/24 15:12
Start Date: 11/Dec/24 15:12
Worklog Time Spent: 10m
Work Description: jbonofre commented on PR #1364:
URL: https://github.com/apache/activemq/pull/1364#issuecomment-2536272913
My point is that async exists for a while in ActiveMQ. So, it makes sense to
use this for spec impl. That's especially true for async send. For message
listener/callback, I think it depends if the user is an existing ActiveMQ user
or a new one.
I would advocate that as a first shot, it makes sense to start from our
ActiveMQ experience.
Issue Time Tracking
-------------------
Worklog Id: (was: 947795)
Time Spent: 2h 50m (was: 2h 40m)
> Implement JMS 2.0 MessageProducer CompletionListener methods
> ------------------------------------------------------------
>
> Key: AMQ-8324
> URL: https://issues.apache.org/jira/browse/AMQ-8324
> Project: ActiveMQ Classic
> Issue Type: New Feature
> Reporter: Matt Pavlovich
> Assignee: Matt Pavlovich
> Priority: Major
> Labels: #jms2
> Fix For: 6.2.0
>
> Time Spent: 2h 50m
> Remaining Estimate: 0h
>
> CompletionListener, etc
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact
