Keith Wall created QPID-7498:
--------------------------------

             Summary: RabbitMQ 0-91 client cannot receive Qpid Client's 
MapMessage
                 Key: QPID-7498
                 URL: https://issues.apache.org/jira/browse/QPID-7498
             Project: Qpid
          Issue Type: Bug
          Components: Java Client
    Affects Versions: 0.17
            Reporter: Keith Wall


RabbitMQ.Client has the ability to read map messages and stream messages 
encoded in Qpid's original map and stream encoding format.  Since 0.8 (work of 
QPID-2363) the format of the map encoding changed to the AMQP 0-10 style, 
breaking this compatibility.  An analogous AMQP 0-10 StreamMessage encoding was 
also introduced but this option is not enabled by default.

Users interoperating with RabbitMQ *might* be able to use the 
{{legacyMapMessageFormat}} and {{legacyStreamMessageFormat}} of the Qpid Java 
Client to workaround this issue.   This won't help users wanting to rely on the 
message conversion features of the Qpid Java Broker, as the conversion layer 
does not consider payloads.

https://www.rabbitmq.com/releases/rabbitmq-dotnet-client/v2.8.6/rabbitmq-dotnet-client-2.8.6-client-htmldoc/html/type-RabbitMQ.Client.Content.StreamMessageReader.html
https://www.rabbitmq.com/releases/rabbitmq-dotnet-client/v2.8.6/rabbitmq-dotnet-client-2.8.6-client-htmldoc/html/type-RabbitMQ.Client.Content.MapMessageReader.html

 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

Reply via email to