[PROTON-666] TransactionalState applied to indicate the txn-id before sending has no effect on the outgoing transfer frames

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: proton-0.7
• Fix Version/s: proton-0.8
• Component/s: proton-j
• Assignee: Robbie Gemmell
• Reporter: Robbie Gemmell
• Created: 09/Sep/14 16:08
• Updated: 07/Jan/16 11:36
• Resolved: 11/Sep/14 08:10

Description

In order to publish messages in a transaction, it is necessary to apply state to the outgoing transfer frames. Proton-J does allow applying a disposition change to the delivery with the relevant TransactionalState (which contains the required txn-id), however this has no impact on the transfer frames which then get emitted from the transport, resulting in the message transfers being considered non-transactional.

The transport implementation should be updated to apply existing local delivery state to the outgoing transfer frames.

Issue Links

• is related to: PROTON-667 add support for transactional state and enable outgoing transfer frames to specify a txn-id