[
https://issues.apache.org/jira/browse/ARTEMIS-536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15299772#comment-15299772
]
Robbie Gemmell commented on ARTEMIS-536:
----------------------------------------
The changes only looked to adjust the output body between being
'AmqpValue(valueList)' or 'AmqpSequence(elementsList)'. Is that correct? If so
that wouldn't be consistent with a 'list inside a sequence' unless the
alternative amqp-value contained a list inside a list (or else there is a bug
in the encoder, and possibly decoder also to match/mask it).
As I say, a sequence section is just a type of list:
{noformat}
<type name="amqp-sequence" class="restricted" source="list" provides="section">
<descriptor name="amqp:amqp-sequence:list" code="0x00000000:0x00000076"/>
</type>
{noformat}
As such it is essentially encoded as a list on the wire, with an expanded
descriptor to indiate it is a sequence section, so unless there were nested
lists in the encoding its wouldnt be a list inside a sequence. Do you have an
example of the encoded bytes?
> AMQP List messages are decoded properly on outbound
> ---------------------------------------------------
>
> Key: ARTEMIS-536
> URL: https://issues.apache.org/jira/browse/ARTEMIS-536
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Reporter: Martyn Taylor
> Assignee: Martyn Taylor
> Fix For: 1.3.0
>
>
> The AMQP-JMS transformer does not distinguish between amqp:sequence and
> amqp:list types. This can result in decoding of incorrect message body. If
> a list type is sent from a client, the decoder may decode it as a sequence
> type, with a single list element.
> This can result in:
> Client sends [foo, bar]
> Client receives [[foo, bar]]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
