qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Wall (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (QPID-6572) 0-10 exchange.unbind does not raise exception if there is no matching binding-key
Date Fri, 05 Jun 2015 11:30:00 GMT

     [ https://issues.apache.org/jira/browse/QPID-6572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Keith Wall updated QPID-6572:
    Labels: amqp_compliance  (was: )

> 0-10 exchange.unbind does not raise exception if there is no matching binding-key 
> ----------------------------------------------------------------------------------
>                 Key: QPID-6572
>                 URL: https://issues.apache.org/jira/browse/QPID-6572
>             Project: Qpid
>          Issue Type: Bug
>          Components: C++ Broker, Java Broker
>    Affects Versions: 0.32
>            Reporter: Keith Wall
>              Labels: amqp_compliance
> exchange.unbind implementations (within the Java Broker and CPP Broker) do not comply
with 0-10 specification with regard to the binding key argument validation.  The spec insists
that the argument is present and must match a binding and that a exception must be thrown
if this is not the case.
> bq. Exception: non-existent-binding-key If there is no matching binding-key the server
MUST raise an exception.
> Neither the Java nor the CPP implementation do this.
> There is also a behavioural difference between the two implementations.  For fanout exchange
type the CPP broker disregards the binding-key argument - meaning that the Python test tests.src.py.qpid_tests.broker_0_10.exchange.AutodeleteTests#testAutodeleteFanout
passes even though it passes a empty binding-key argument.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org

View raw message