[
https://issues.apache.org/jira/browse/QPID-4146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Moravec updated QPID-4146:
--------------------------------
Attachment: bz726687.patch
See client/src/main/java/org/apache/qpid/client/AMQSession_0_10.java file:
sendQueueBind method (that invokes getQpidSession().exchangeBind method for
requesting the binding to be created) is called from
handleAddressBasedDestination just for AMQDestination.QUEUE_TYPE case. I.e.
only when the node is queue type and not topic.
The call of the sendQueueBind method should be irrelevant whether the node is
queue or topic and whether the node already exists or not. It should be called
only when the create: policy evaluates to true.
> JMS client: node binding not created for topic node
> ---------------------------------------------------
>
> Key: QPID-4146
> URL: https://issues.apache.org/jira/browse/QPID-4146
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Affects Versions: 0.14
> Reporter: Pavel Moravec
> Priority: Trivial
> Labels: patch
> Attachments: bz726687.patch
>
>
> When creating a topic (an exchange in qpid terminology) with x-bindings
> within node: scope, the binding is not created. See this simple reproducer:
> qpid-config add queue q
> export CLASSPATH=$(find "/usr/share/java/" -name '*.jar' | tr '\n' ":")
> cd /usr/share/doc/qpid-java-0.14/examples
> ./run_example.sh org.apache.qpid.example.Spout --content="msg1" "ex/key;{
> create: always, node: { type: topic, x-bindings: [{ exchange:'ex', queue:
> 'q', key: 'key' }]}}"
> qpid-config exchanges -b then shows no binding from 'ex' exchange.
> Simple patch to be attached.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
