[ 
https://issues.apache.org/jira/browse/QPIDIT-46?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16406680#comment-16406680
 ] 

ASF subversion and git services commented on QPIDIT-46:
-------------------------------------------------------

Commit b87dc72a330724d6d888d87faa567d003a2e5c07 in qpid-interop-test's branch 
refs/heads/master from [~kpvdr]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-interop-test.git;h=b87dc72 ]

QPIDIT-46: Added encoding for AMQP list and map types, and which can contain 
other lists and maps. This has been completed on the ProtonCpp and 
ProtonPython{2,3} shims, and RheaJs and AmqpNetLite have this test disabled for 
now.


> Correctly encode AMQP types within complex types list and map
> -------------------------------------------------------------
>
>                 Key: QPIDIT-46
>                 URL: https://issues.apache.org/jira/browse/QPIDIT-46
>             Project: Apache QPID Interoperability Test Suite
>          Issue Type: Bug
>          Components: AMQP Types Test, Proton C++ Shim, Proton Python Shim, 
> Rhea JavaScript Shim
>    Affects Versions: 0.1.0
>            Reporter: Kim van der Riet
>            Assignee: Kim van der Riet
>            Priority: Major
>
> 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.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

Reply via email to