[
https://issues.apache.org/jira/browse/PROTON-2236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17125208#comment-17125208
]
ASF subversion and git services commented on PROTON-2236:
---------------------------------------------------------
Commit 9adf419eab623e363422bf89d79b5884c747a644 in qpid-proton-j's branch
refs/heads/master from Timothy Bish
[ https://gitbox.apache.org/repos/asf?p=qpid-proton-j.git;h=9adf419 ]
PROTON-2236 Report more meaningful unexpected encoding errors
When the decoder reads a type encoding that does not match the
encoding code of the primitive type expected then report a more
menaingful error including the type expected and the type / code
that was read, or unknown / code if type code read is not valid.
> [proton-j] Error message when decoding illegal message properties key is
> unhelpful
> ----------------------------------------------------------------------------------
>
> Key: PROTON-2236
> URL: https://issues.apache.org/jira/browse/PROTON-2236
> Project: Qpid Proton
> Issue Type: Improvement
> Components: proton-j
> Reporter: Kim van der Riet
> Priority: Trivial
>
> While decoding a message containing a non-string application-properties key
> (eg a symbol key), then the following message is seen:
> {{Error on transform: Expected String type but found encoding: -93}}
> which is not very intuitive. Perhaps converting the type to hex and providing
> a stringified version would be better, such as:
> {{Expected String type but found encoding 0xb3 (symbol)}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
