Uploaded image for project: 'Qpid Proton'
  1. Qpid Proton
  2. PROTON-1097

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

    Details

    • 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
    • Labels:
      None

      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

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                gemmellr Robbie Gemmell
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated: