[QPIDIT-46] Correctly encode AMQP types within complex types list and map

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 0.1.0
• Fix Version/s: 0.2.0
• Component/s: AMQP Types Test, Proton C++ Shim, Proton Python Shim, Rhea JavaScript Shim
• Assignee: Kim van der Riet
• Reporter: Kim van der Riet
• Created: 04/Nov/16 12:45
• Updated: 18/Oct/21 16:47
• Resolved: 30/Apr/18 16:52

Description

Currently the AMQP type tests for list and map are using only strings. An extra step for encoding/decoding these on the Sender/Receiver shims are needed. At present, the list and map keys and elements are created using a string format "type:value", but these are simply being used as-is as string literals.

Currently all shim tests for these types pass.

Issue Links

• is duplicated by: QPIDIT-77 Shims always send list items as well as map values and keys encoded as string