[ 
https://issues.apache.org/jira/browse/QPID-7694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15902851#comment-15902851
 ] 

Keith Wall edited comment on QPID-7694 at 3/9/17 10:26 AM:
-----------------------------------------------------------

We will generalise this.  Any queue/exchange/consumer declare arguments that 
match a know attribute should be acceptable as if they were wire arguments.    
Existing wire arguments should retain their existing semantics.   If arguments 
contain both a wire argument and its model attribute counterpart, the wire 
argument should take precedence in order that existing behaviour is not 
changed.     Arguments that aren't recognised should continue to be ignored.




was (Author: k-wall):
We will generalise this.  Any queue/exchange/consumer declare arguments that 
match a know attribute should be acceptable as if they were wire arguments.    
Existing wire arguments should retain there existing semantics.   If arguments 
contain both a wire argument and its model attribute counterpart, the wire 
argument should take precedence in order that existing behaviour is not 
changed.     Arguments that aren't recognised should continue to be ignored.



> Add 0-8..0-10 wire queue declare argument for holds on publish
> --------------------------------------------------------------
>
>                 Key: QPID-7694
>                 URL: https://issues.apache.org/jira/browse/QPID-7694
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Java Broker
>            Reporter: Keith Wall
>             Fix For: qpid-java-broker-7.0.0
>
>
> From an ADDR address, I ought to be able to specify that the queue is 
> declared with holdOnPublishEnabled enabled.    Currently 
> Queue#holdOnPublishEnabled is not mapped to a wire argument, so this is not 
> possible,



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to