You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Alex Rudyy (Updated) (JIRA)" <ji...@apache.org> on 2011/11/07 18:26:51 UTC
[jira] [Updated] (QPID-3519) Refactor the logic behind sending of
the selector arguments during subscription creation
[ https://issues.apache.org/jira/browse/QPID-3519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Rudyy updated QPID-3519:
-----------------------------
Attachment: 0001-QPID-3519-refactor-consumer-argument-handling.patch
> Refactor the logic behind sending of the selector arguments during subscription creation
> ----------------------------------------------------------------------------------------
>
> Key: QPID-3519
> URL: https://issues.apache.org/jira/browse/QPID-3519
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Reporter: Robbie Gemmell
> Assignee: Alex Rudyy
> Fix For: 0.14
>
> Attachments: 0001-QPID-3519-refactor-consumer-argument-handling.patch
>
>
> In current implementation the FieldTable with JMS selector is created in AMQSession#createConsumerImpl.
> The 0-8 MessageConsumer code creates a new FieldTable objects when sending its BasicConsime method.
> The 0-10 AMQSession code does send an arguments map sourced from the consumer when doing the 'sendConsume' method.
> Also, both clients send FieldTable with the selector argument they do it using different FieldTable objects.
> This needs to be improved to allow both clients to reuse the same code.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org