[
https://issues.apache.org/jira/browse/QPIDJMS-624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18101460#comment-18101460
]
ASF subversion and git services commented on QPIDJMS-624:
---------------------------------------------------------
Commit 452589ad695aed9b8b6d3fd1e510748e81cbb5f9 in qpid-jms's branch
refs/heads/main from David Voit
[ https://gitbox.apache.org/repos/asf?p=qpid-jms.git;h=452589ad ]
QPIDJMS-624 Also support non-byte type-annotations
NMS AMQP is using "byte" which are unsigned in dotnet.
Yes, this is non-std compatible, but not handling these values
is also non-std compatible.
It's a MUST to sent data as signed byte.
But it's also a MUST to read other numeric values in the
type-annotations fields in the binding spec.
> AMQP JMS Binding Type Annotations should also support non-byte datatypes
> ------------------------------------------------------------------------
>
> Key: QPIDJMS-624
> URL: https://issues.apache.org/jira/browse/QPIDJMS-624
> Project: Qpid JMS
> Issue Type: Improvement
> Reporter: David Voit
> Priority: Minor
>
> In the AMQP JMS spec Type Annotations are definied to be of byte type.
> NMS AMQP had a bug which was sending these annotation as an unsigned byte.
> This is a bug in NMS Amqp. But the spec also says that a conforming
> implementation on the recieving side, should support all numeric data types,
> not just signed bytes.
> It will take some time to fix all nms amqp clients to switch to an release
> (which not yet even happened) which no longer has this problem. Also this
> change also makes the code more error resilant, and the change is quite
> trivial
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
