jakartaee / jakartaee/messaging
Introduce a new mode: INDIVIDUAL_ACKNOWLEDGE
- Dominant language
- Java
- Stars
- 49
- Forks
- 34
- PR merge metrics
- No merged PRs in 30d
Description
Many messaging systems, like Apache Pulsar with Shared subscriptions, support acknowledging single messages.
Current Session.CLIENT_ACKNOWLEDGE requires that all the messages dispatched by the session have to be acknowledged and not only that single message.
Some references:
- Apache Pulsar via Starlight for JMS: https://github.com/datastax/pulsar-jms/pull/30
- Apache ActiveMQ Artemis: https://activemq.apache.org/components/artemis/documentation/latest/pre-acknowledge.html
Contributor guide
Research direction
Start by reading the Jakarta Messaging specification around Session.CLIENT_ACKNOWLEDGE and compare the referenced Pulsar JMS and ActiveMQ Artemis behavior. Define the semantics and compatibility requirements for INDIVIDUAL_ACKNOWLEDGE, then identify the specification and test locations that must demonstrate single-message acknowledgement.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100