[ https://issues.apache.org/jira/browse/QPIDJMS-259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16995215#comment-16995215 ]
Neeraj Makam commented on QPIDJMS-259: -------------------------------------- Bumping up for visibility... I am also looking for this change. Is there a way for vendor specific properties to be set on performatives? > Allow client to influence the attach properties of the link underlying a > consumer > --------------------------------------------------------------------------------- > > Key: QPIDJMS-259 > URL: https://issues.apache.org/jira/browse/QPIDJMS-259 > Project: Qpid JMS > Issue Type: Improvement > Components: qpid-jms-client > Reporter: Keith Wall > Priority: Major > > As a user of the Qpid JMS Client, I currently have no way to enable features > of the Qpid Broker for Java's features such as consumer priority or arrival > time filtering. > To enable these features for AMQP 1.0 I need a way to influence the link > attachment properties that are sent when the JMS Consumer is created. > In the 0-x Qpid JMS Client the Destination addresses were overloaded with > this extra information. Binding URLs had special arguments such as > {{x-priority='10'}} which the client, with hardcoded knowledge, knew had to > be passed to {{basic.consume}}/{{message.subscribe}}. ADDRs were slightly > nicer insofar as the subscribe arguments cold be set to arbitrary name/value > pairs. Encoding the information in the address, whilst ugly, did mean users > of the messaging integration products (such as Spring), could access the > features without coding. > It would be nice if the Qpid JMS Client had an unobtrusive vendor specific > mechanism, that allows a application to influence the properties of any AMQP > performative. -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org