[
https://issues.apache.org/jira/browse/QPIDJMS-121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell updated QPIDJMS-121:
-----------------------------------
Description:
Updated Description:
Add the ability to set the AMQP disposition type used when when acknowledging
messages while using client-acknowledge mode.
The particular disposition to be applied will be set using the message object
that the acknowledge method is called on, using a vendor property selected by
the AMQP BINDMAP TC. As with the defined JMS behaviour in CLIENT_ACKNOWLEDGE
mode, all messages on the session seen by the application and not yet
acknowledged will have the disposition applied to them.
This is an updated approach following discussion of the original proposal
detailed below.
Original Description:
description from GitHub README. README and code changes located here:
https://github.com/andrew-buckley/qpid-jms/
h1. QpidJMS with AMQP-style acknowledgements
This is a fork of the QpidJMS project that adds the ability to acknowledge
messages in three ways: CONSUMED, POISONED, and RELEASED.
The fork is based on QpidJMS version 0.4.0-SNAPSHOT but has been merged with
the current unreleased 0.6.0. The fork is
fully compatible with JMS 1.1 but provides an additional interface,
JmsAmqpMessage
(found in org.apache.qpid.jms), that features this new functionality.
Any messages consumed using this provider can be safely cast to type
JmsAmpqMessage.
h2. Additions
* org.apache.qpid.jms.message.JmsAmqpMessage
* org.apache.qpid.jms.message.JmsAcknowledgeCallback
h2. Changes
* Added method acknowledge(ProviderConstants.ACK_TYPE ackType) to
org.apache.qpid.jms.message.JmsMessage.
* Changed acknowledgeCallback type in org.apache.qpid.jms.message.JmsMessage to
type JmsAcknowledgeCallback.
* Changed method onInboundMessage in org.apache.qpid.jms.JmsMessageConsumer to
set a message callback
that takes an ACK_TYPE as an argument.
* Changed method acknowledge() in org.apache.qpid.jms.JmsSession to take an
ACK_TYPE as an argument.
* Changed method acknowledge(JmsSessionId sessionId) in
org.apache.qpid.jms.JmsConnection to take an ACK_TYPE
as an argument.
* Changed method acknowledge(final JmsSessionId sessionId, final AsyncResult
request) in
org.apache.qpid.jms.provider.amqp.AmqpProvider to take an ACK_TYPE as an
argument.
* Changed method acknowledge() in org.apache.qpid.jms.provider.amqp.AmqpSession
to take an ACK_TYPE
as an argument.
* Changed method acknowledge() in
org.apache.qpid.jms.provider.amqp.AmqpConsumer to take an ACK_TYPE
as an argument. The method maps acknowledgement types to AMQP dispositions as
follows:
CONSUMED to ACCEPTED, POISONED to REJECTED, RELEASED to RELEASED.
was:
description from GitHub README. README and code changes located here:
https://github.com/andrew-buckley/qpid-jms/
h1. QpidJMS with AMQP-style acknowledgements
This is a fork of the QpidJMS project that adds the ability to acknowledge
messages in three ways: CONSUMED, POISONED, and RELEASED.
The fork is based on QpidJMS version 0.4.0-SNAPSHOT but has been merged with
the current unreleased 0.6.0. The fork is
fully compatible with JMS 1.1 but provides an additional interface,
JmsAmqpMessage
(found in org.apache.qpid.jms), that features this new functionality.
Any messages consumed using this provider can be safely cast to type
JmsAmpqMessage.
h2. Additions
* org.apache.qpid.jms.message.JmsAmqpMessage
* org.apache.qpid.jms.message.JmsAcknowledgeCallback
h2. Changes
* Added method acknowledge(ProviderConstants.ACK_TYPE ackType) to
org.apache.qpid.jms.message.JmsMessage.
* Changed acknowledgeCallback type in org.apache.qpid.jms.message.JmsMessage to
type JmsAcknowledgeCallback.
* Changed method onInboundMessage in org.apache.qpid.jms.JmsMessageConsumer to
set a message callback
that takes an ACK_TYPE as an argument.
* Changed method acknowledge() in org.apache.qpid.jms.JmsSession to take an
ACK_TYPE as an argument.
* Changed method acknowledge(JmsSessionId sessionId) in
org.apache.qpid.jms.JmsConnection to take an ACK_TYPE
as an argument.
* Changed method acknowledge(final JmsSessionId sessionId, final AsyncResult
request) in
org.apache.qpid.jms.provider.amqp.AmqpProvider to take an ACK_TYPE as an
argument.
* Changed method acknowledge() in org.apache.qpid.jms.provider.amqp.AmqpSession
to take an ACK_TYPE
as an argument.
* Changed method acknowledge() in
org.apache.qpid.jms.provider.amqp.AmqpConsumer to take an ACK_TYPE
as an argument. The method maps acknowledgement types to AMQP dispositions as
follows:
CONSUMED to ACCEPTED, POISONED to REJECTED, RELEASED to RELEASED.
> add ability to send different AMQP dispositions when using client-acknowledge
> mode
> ----------------------------------------------------------------------------------
>
> Key: QPIDJMS-121
> URL: https://issues.apache.org/jira/browse/QPIDJMS-121
> Project: Qpid JMS
> Issue Type: New Feature
> Components: qpid-jms-client
> Affects Versions: 0.6.0
> Reporter: Andrew Buckley
> Assignee: Robbie Gemmell
> Fix For: 0.7.0
>
>
> Updated Description:
> Add the ability to set the AMQP disposition type used when when acknowledging
> messages while using client-acknowledge mode.
> The particular disposition to be applied will be set using the message object
> that the acknowledge method is called on, using a vendor property selected by
> the AMQP BINDMAP TC. As with the defined JMS behaviour in CLIENT_ACKNOWLEDGE
> mode, all messages on the session seen by the application and not yet
> acknowledged will have the disposition applied to them.
> This is an updated approach following discussion of the original proposal
> detailed below.
> Original Description:
> description from GitHub README. README and code changes located here:
> https://github.com/andrew-buckley/qpid-jms/
> h1. QpidJMS with AMQP-style acknowledgements
> This is a fork of the QpidJMS project that adds the ability to acknowledge
> messages in three ways: CONSUMED, POISONED, and RELEASED.
> The fork is based on QpidJMS version 0.4.0-SNAPSHOT but has been merged with
> the current unreleased 0.6.0. The fork is
> fully compatible with JMS 1.1 but provides an additional interface,
> JmsAmqpMessage
> (found in org.apache.qpid.jms), that features this new functionality.
> Any messages consumed using this provider can be safely cast to type
> JmsAmpqMessage.
> h2. Additions
> * org.apache.qpid.jms.message.JmsAmqpMessage
> * org.apache.qpid.jms.message.JmsAcknowledgeCallback
> h2. Changes
> * Added method acknowledge(ProviderConstants.ACK_TYPE ackType) to
> org.apache.qpid.jms.message.JmsMessage.
> * Changed acknowledgeCallback type in org.apache.qpid.jms.message.JmsMessage
> to type JmsAcknowledgeCallback.
> * Changed method onInboundMessage in org.apache.qpid.jms.JmsMessageConsumer
> to set a message callback
> that takes an ACK_TYPE as an argument.
> * Changed method acknowledge() in org.apache.qpid.jms.JmsSession to take an
> ACK_TYPE as an argument.
> * Changed method acknowledge(JmsSessionId sessionId) in
> org.apache.qpid.jms.JmsConnection to take an ACK_TYPE
> as an argument.
> * Changed method acknowledge(final JmsSessionId sessionId, final AsyncResult
> request) in
> org.apache.qpid.jms.provider.amqp.AmqpProvider to take an ACK_TYPE as an
> argument.
> * Changed method acknowledge() in
> org.apache.qpid.jms.provider.amqp.AmqpSession to take an ACK_TYPE
> as an argument.
> * Changed method acknowledge() in
> org.apache.qpid.jms.provider.amqp.AmqpConsumer to take an ACK_TYPE
> as an argument. The method maps acknowledgement types to AMQP dispositions as
> follows:
> CONSUMED to ACCEPTED, POISONED to REJECTED, RELEASED to RELEASED.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
