You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@qpid.apache.org by "Timothy A. Bish (Jira)" <ji...@apache.org> on 2026/08/03 18:14:00 UTC

[jira] [Resolved] (QPIDJMS-624) AMQP JMS Binding Type Annotations should also support non-byte datatypes

     [ https://issues.apache.org/jira/browse/QPIDJMS-624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timothy A. Bish resolved QPIDJMS-624.
-------------------------------------
    Fix Version/s: 1.17.0
                   2.11.0
         Assignee: Timothy A. Bish
       Resolution: Fixed

> 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
>            Assignee: Timothy A. Bish
>            Priority: Minor
>             Fix For: 1.17.0, 2.11.0
>
>
> 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: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org