[
https://issues.apache.org/jira/browse/ARTEMIS-536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15299926#comment-15299926
]
Robbie Gemmell commented on ARTEMIS-536:
----------------------------------------
Yes, that just looks like a sequence witih a single string element to me, so
I'd say thats potentially a client issue too if it thinks otherwise. Its not
wrong to be concerned that it sent a amqp-value+list and got a sequence back,
but it doesn't look like a sequence containing an element that is itself a list.
> 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)
