[
https://issues.apache.org/jira/browse/PROTON-775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Darryl L. Pierce updated PROTON-775:
------------------------------------
Attachment: 0001-PROTON-775-Ensure-that-annotation-keys-in-Ruby-are-e.patch
This patch changes how annotations are encoded to ensure that the keys are sent
as symbols.
> ruby: message annotations send from a ruby client are invalid
> -------------------------------------------------------------
>
> Key: PROTON-775
> URL: https://issues.apache.org/jira/browse/PROTON-775
> Project: Qpid Proton
> Issue Type: Bug
> Components: ruby-binding
> Affects Versions: 0.8
> Reporter: Dominic Evans
> Assignee: Darryl L. Pierce
> Attachments:
> 0001-PROTON-775-Ensure-that-annotation-keys-in-Ruby-are-e.patch
>
>
> Since PROTON-616, proton-j has attempted to enforce the fact that the key's
> of a message annotations map *must* be of the Symbol type (or actually ulong,
> but those are reserved so we don't need to worry about that) [1]
> Unfortunately, from the Ruby client, the mapping of a native map into proton
> data always sets the key's as strings rather than symbols.
> In proton-j, you'll currently hit a `java.lang.ClassCastException:
> java.lang.String incompatible with org.apache.qpid.proton.amqp.Symbol` if you
> try to look at keys of the MessageAnnotations object of a message sent from
> the ruby send.rb example (which sets message annotations for the keys
> 'version' and 'pill').
> --
> [1]
> http://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core-messaging-v1.0-os.html#type-annotations
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
