You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2018/11/28 12:43:00 UTC

[jira] [Commented] (QPID-7642) [Java Broker] Create binding operations on exchanges should fail when invalid selector is provided as part of binding arguments

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

ASF subversion and git services commented on QPID-7642:
-------------------------------------------------------

Commit e1d8e2fd84123cc518b82a4f7c4cd5fd46244d96 in qpid-broker-j's branch refs/heads/master from [~alex.rufous]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=e1d8e2f ]

QPID-7642: [Broker-J] Let caller to handle bind operation exception for invalid selector


> [Java Broker] 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
>            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: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org