You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Kim van der Riet (JIRA)" <ji...@apache.org> on 2017/06/15 20:38:00 UTC

[jira] [Updated] (PROTON-1505) Message header defaults only work if no header present

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

Kim van der Riet updated PROTON-1505:
-------------------------------------
    Summary: Message header defaults only work if no header present  (was: [C++, python binding] Message header defaults not supported)

> Message header defaults only work if no header present
> ------------------------------------------------------
>
>                 Key: PROTON-1505
>                 URL: https://issues.apache.org/jira/browse/PROTON-1505
>             Project: Qpid Proton
>          Issue Type: Bug
>          Components: proton-c
>            Reporter: Kim van der Riet
>            Assignee: Cliff Jansen
>
> An error in the qpid-interop-tests JMS headers test showed that where there is no message header on the wire, the C++ and Python client APIs do not return the default value as mandated by the AMQP spec. In particular, the priority is returned with a value of 0 rather than the default value of 4.
> This raises two issues:
> 1. Setting the default value (in particularly for priority, where a priority system may be adopted that is not default, and the missing value may need to have a value other than 4). 
> 2. (C++) Gaining access to the transport headers so that there is an ability to distinguish between the default and the value being actually present on the wire.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org