You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Jonathan Robie (JIRA)" <qp...@incubator.apache.org> on 2010/04/09 18:02:50 UTC
[jira] Created: (QPID-2495) CLONE - Node assertions don't work for
node-property types ( topic, queue )
CLONE - Node assertions don't work for node-property types ( topic, queue )
---------------------------------------------------------------------------
Key: QPID-2495
URL: https://issues.apache.org/jira/browse/QPID-2495
Project: Qpid
Issue Type: Bug
Components: C++ Client
Reporter: Jonathan Robie
Asserting the wrong node property type seems to have no effect on address
resolution in the drain example:
$ ./drain -a "amq.direct/foo; { assert: always, node-properties: { type: topic
}}"
$ ./drain -a "amq.direct/foo; { assert: always, node-properties: { type: queue
}}"
$ ./drain -a "amq.fanout; { assert: always, node-properties: { type: queue }}"
$ ./drain -a "amq.fanout; { assert: always, node-properties: { type: topic }}"
The program seems to actually resolve the address, and can receive messages,
even if the assertion does not match, and this is not limited to pre-declared
exchanges:
$ ./drain -a "fanout-exchange; { assert: always, node-properties: { type: queue
}}" -t 30
Message(properties={spout-id:1f32f14f-8cff-4a51-8bed-bac7fe84f00e:0},
content='')
It doesn't work for assertions on queues, either:
$ ./drain -a "xoxox; { assert: always, node-properties: { type: topic }}"
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] Deleted: (QPID-2495) CLONE - Node assertions don't work for
node-property types ( topic, queue )
Posted by "Jonathan Robie (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-2495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Robie deleted QPID-2495:
---------------------------------
> CLONE - Node assertions don't work for node-property types ( topic, queue )
> ---------------------------------------------------------------------------
>
> Key: QPID-2495
> URL: https://issues.apache.org/jira/browse/QPID-2495
> Project: Qpid
> Issue Type: Bug
> Reporter: Jonathan Robie
>
> Asserting the wrong node property type seems to have no effect on address
> resolution in the drain example:
> $ ./drain -a "amq.direct/foo; { assert: always, node-properties: { type: topic
> }}"
> $ ./drain -a "amq.direct/foo; { assert: always, node-properties: { type: queue
> }}"
> $ ./drain -a "amq.fanout; { assert: always, node-properties: { type: queue }}"
> $ ./drain -a "amq.fanout; { assert: always, node-properties: { type: topic }}"
> The program seems to actually resolve the address, and can receive messages,
> even if the assertion does not match, and this is not limited to pre-declared
> exchanges:
> $ ./drain -a "fanout-exchange; { assert: always, node-properties: { type: queue
> }}" -t 30
> Message(properties={spout-id:1f32f14f-8cff-4a51-8bed-bac7fe84f00e:0},
> content='')
> It doesn't work for assertions on queues, either:
> $ ./drain -a "xoxox; { assert: always, node-properties: { type: topic }}"
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org