[
https://issues.apache.org/jira/browse/QPID-3444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115056#comment-13115056
]
Robbie Gemmell commented on QPID-3444:
--------------------------------------
Correct, but I dont think that strictly relates to this issue, and instead our
somewhat shoddy implementation of the default exchange. That problem arises due
to the default exchange actually having a name when it isnt meant to (thus the
changes in this JIRA to protect it as nameless), which I think should be
bundled into QPID-3490 (which didnt actually mention that, although it is
something I was looking to include there - updated accordingly).
> the Java broker does not reject 0-10 exchange delete/bind/unbind commands
> which use empty strings for the exchange name
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: QPID-3444
> URL: https://issues.apache.org/jira/browse/QPID-3444
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: 0.6, 0.7, 0.8, 0.9, 0.10, 0.11, 0.12
> Reporter: Robbie Gemmell
> Assignee: Robbie Gemmell
> Fix For: 0.13
>
>
> The Java broker [sometimes] verifies that the 0-10 exchange
> delete/bind/unbind commands have an exchange value set however it does not
> reject those which have an empty string defined, which is interpreted as the
> default exchange. It should issue an INVALID_ARGUMENT exception if the
> exchange name is null or empty for these commands.
--
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:[email protected]
