[
https://issues.apache.org/jira/browse/QPID-2354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12832126#action_12832126
]
Sam Hendley commented on QPID-2354:
-----------------------------------
Yikes, this is an ugly bug. I took a look at fixing this but its a relatively
major undertaking. The issue stems from using the same set of attributes for
carrying user information to carry internal information. collisions were bound
to occur. the same thing will happen with an 'id' field.
I also found that the "exchange-query-result" type has a field called type as
well, I think this would suffer the same problem so I changed that one as well.
Does this occur in the python client?
> ruby client exchange declaration doesn't allow 'type' argument
> --------------------------------------------------------------
>
> Key: QPID-2354
> URL: https://issues.apache.org/jira/browse/QPID-2354
> Project: Qpid
> Issue Type: Bug
> Components: Ruby Client
> Affects Versions: 0.5
> Environment: Ubuntu/Qpid-0.5
> Reporter: Andrea Barisani
>
> Due to the way function arguments are treated/overrided in the driver it is
> currently impossible to issue the following command:
> session.exchange_declare(name, :type => 'fanout')
> as the :type variable is shadowed within qpid/datatypes.rb struct method.
> A quick workaround is changing the xml spec with a different name (very nasty
> though) and everything works (confirming that the attribute is actually
> honoured).
> Cheers
--
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:[email protected]
