[PROTON-1097] [proton-j] validate details for message-format value on received transfers

• Type: Bug
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: proton-0.12.0
• Fix Version/s: proton-j-future
• Component/s: proton-j
• Assignee: Unassigned
• Reporter: Robbie Gemmell
• Created: 13/Jan/16 15:39
• Updated: 19/Jul/17 21:22

Description

The spec [1] notes various details for the message-format field which we dont currently enforce, such as that it must be present on the first transfer of a multi-transfer message, can be omitted on continuations, and that [if set] it is an error for the format on a contituation to differ from the first transfer.

Previously the format was alwayss et to 0 on outgoing transfers, and never used/inspected at all on incoming transfers, with the Delivery#getMessageFormat() method always returning 0. Following PROTON-1096, the value on the first transfer for a message is used to update the message-format value returned from the Delivery object.

[1] http://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core-transport-v1.0-os.html#type-transfer

Issue Links

• is blocked by: PROTON-281 Engine should handle errors by generating implicit CLOSE frame
• relates to: PROTON-1038 message-format on received transfer is never checked (nor made available for application to check)
• relates to: PROTON-1096 [proton-j] enable set/get of MessageFormat on the Delivery being sent/received