You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Justin Ross (JIRA)" <ji...@apache.org> on 2016/11/04 16:44:58 UTC
[jira] [Updated] (PROTON-776) proton-j: Message.decode doesn't
validate all data types?
[ https://issues.apache.org/jira/browse/PROTON-776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Justin Ross updated PROTON-776:
-------------------------------
Labels: codec (was: )
> proton-j: Message.decode doesn't validate all data types?
> ---------------------------------------------------------
>
> Key: PROTON-776
> URL: https://issues.apache.org/jira/browse/PROTON-776
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-j
> Affects Versions: 0.8
> Reporter: Dominic Evans
> Labels: codec
> Fix For: Future
>
>
> PROTON-616 attempted to enfore that message annotation keys were of the Symbol type. However, it seems to be possible to send a map with strings keys for the message annotations section (e.g., via the ruby client) and message.decode will accept this.
> It is only when you try to use the MessageAnnotations map that you get a `java.lang.ClassCastException: java.lang.String incompatible with org.apache.qpid.proton.amqp.Symbol` exception because the underlying map isn't compatible with what the generics suggest.
> Isn't this something that we should catch at decode time?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org