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

Rajith Attapattu commented on QPID-4497:
----------------------------------------

As to your original question about a test for this specific case (of being able 
to override subscription queue properties) exists ?
The answer to that question is we do have a test.

As to whether we have adequate coverage for assertion and error handling in 
general, then the answer is no. There was a gap (and possibly more) and the 
fact that this issue was masked is a case in point. We do have assert tests 
that are used as part of other tests, but not enough IMO.

As mentioned in QPID-4496 I think we need a better set of tests for this area 
and I'm looking at it atm.
                
> [Java client] Exclusive property for the subscription queue cannot be 
> overridden using the address string
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: QPID-4497
>                 URL: https://issues.apache.org/jira/browse/QPID-4497
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Client
>    Affects Versions: 0.18, 0.20
>            Reporter: Rajith Attapattu
>            Assignee: Rajith Attapattu
>            Priority: Minor
>              Labels: addressing
>             Fix For: 0.21
>
>
> There have been requests to allow the customization of the subscription 
> queue. However there was an issue as the exclusive property wasn't set 
> properly due to a bug.
> amq.topic/test; {link: {name:my-queue, durable:true, 
> x-declare:{exclusive:false, auto-delete:false}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

Reply via email to