[PROTON-1505] Message header defaults only work if no header present

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: proton-c-0.21.0
• Component/s: proton-c
• Labels: codec
• Assignee: Andrew Stitcher
• Reporter: Kim van der Riet
• Created: 15/Jun/17 18:43
• Updated: 26/Mar/18 10:20
• Resolved: 01/Feb/18 23:12

Description

An error in the qpid-interop-tests JMS headers test showed that where there is no message priority 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.

Issue Links

• depends upon: PROTON-1753 Improve protocol.h generation to include default header values
• relates to: PROTON-927 absolute-expiry-time, creation-time are encoded as 0 if not set rather than null