[
https://issues.apache.org/jira/browse/QPIDJMS-220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15675036#comment-15675036
]
ASF subversion and git services commented on QPIDJMS-220:
---------------------------------------------------------
Commit e9682166439b311125c4e156bc40880c16c0f464 in qpid-jms's branch
refs/heads/master from [~tabish121]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-jms.git;h=e968216 ]
QPIDJMS-220 Additional testing of the Subscription Tracker
Add some additional testing of the subscription tracker to cover
expected exceptions and other cases not yet covered.
> add support for shared topic subscriptions
> ------------------------------------------
>
> Key: QPIDJMS-220
> URL: https://issues.apache.org/jira/browse/QPIDJMS-220
> Project: Qpid JMS
> Issue Type: Sub-task
> Components: qpid-jms-client
> Reporter: Robbie Gemmell
> Assignee: Robbie Gemmell
> Fix For: 0.20.0
>
>
> JMS 2.0 adds support for shared volatile and durable topic subscriptions.
> Whilst at its simplest this logically reduces to consuming messages from a
> shared backing queue representing the subscription, there are however many
> details to consider and a mechanism is needed for conveying the required
> details/behaviours using AMQP 1.0. This JIRA serves to capture information
> regarding this, both as it applies to AMQP clients/servers in general, and
> specifically to the JMS client.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]