[
https://issues.apache.org/jira/browse/PROTON-1097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross updated PROTON-1097:
--------------------------------
Fix Version/s: proton-j-0.20.0
> [proton-j] validate details for message-format value on received transfers
> --------------------------------------------------------------------------
>
> Key: PROTON-1097
> URL: https://issues.apache.org/jira/browse/PROTON-1097
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-j
> Affects Versions: 0.12.0
> Reporter: Robbie Gemmell
> Priority: Minor
> Fix For: proton-j-0.20.0
>
>
> 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
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
