[
https://issues.apache.org/jira/browse/ARTEMIS-536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15299824#comment-15299824
]
Martyn Taylor commented on ARTEMIS-536:
---------------------------------------
I see. The descriptor is probably what I was seeing then. The bytes
looked like:
0 83 118 -> Sequence Descriptor
-64 9 1 -> List Constructor
-95 6 -> String Constructor
>From what I was seeing the client was decoding this as [["String"]].
Perhaps this is also a client issue.
Thanks for clarifying.
On Wed, May 25, 2016 at 10:56 AM, Robbie Gemmell (JIRA) <[email protected]>
> 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)
