[
https://issues.apache.org/jira/browse/QPID-7642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy updated QPID-7642:
-----------------------------
Summary: [Broker-J] Create binding operations on exchanges should fail when
invalid selector is provided as part of binding arguments (was: [Java Broker]
Create binding operations on exchanges should fail when invalid selector is
provided as part of binding arguments)
> [Broker-J] Create binding operations on exchanges should fail when invalid
> selector is provided as part of binding arguments
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: QPID-7642
> URL: https://issues.apache.org/jira/browse/QPID-7642
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
> Affects Versions: 0.32, qpid-java-6.0, qpid-java-6.0.1, qpid-java-6.0.2,
> qpid-java-6.0.3, qpid-java-6.0.4, qpid-java-6.0.5, qpid-java-6.1,
> qpid-java-6.0.6, qpid-java-6.1.1
> Reporter: Alex Rudyy
> Assignee: Alex Rudyy
> Priority: Major
> Fix For: qpid-java-broker-7.1.0
>
>
> When create binding operation is invoked with invalid selector provided as
> part of binding arguments , the current exchange implementations react
> differently on this error condition:
> * fanout and direct exchanges create binding successfully without a selector
> * topic exchange throws ConnectionScopeRuntimeException
> * header exchange create "x-exclude-all" filter
> The current behavior is inconsistent and not valid. The caller needs to be
> notified about error condition by throwing a special exception which is not
> ConnectionScopeRuntimeException.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
