[ https://issues.apache.org/jira/browse/PROTON-775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14309115#comment-14309115 ]
Darryl L. Pierce commented on PROTON-775: ----------------------------------------- [~dnwe] is this something we can fix in mapping.rb in MAP.put? If the keys for a map must be a Symbol we should be able to enforce it there, yeah? > 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 > > 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)