[
https://issues.apache.org/jira/browse/QPID-6338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14297869#comment-14297869
]
Mark Soderquist commented on QPID-6338:
---------------------------------------
Sounds like this is not a bug, but I would like to throw out an "it would be
nice". If it's not to much of a performance hit, it would be nice if, when
creating the Message, it would check the section order and throw an exception
if the developer tried to create an invalid message. To help developers like me
realize we did it wrong. :-)
> AMQP 1.0 message not readable with AMQP 1.0 JMS client
> ------------------------------------------------------
>
> Key: QPID-6338
> URL: https://issues.apache.org/jira/browse/QPID-6338
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker, Java Client
> Affects Versions: 0.30
> Environment: java version "1.7.0_71"
> OpenJDK Runtime Environment (rhel-2.5.3.2.el6_6-x86_64 u71-b14)
> OpenJDK 64-Bit Server VM (build 24.65-b04, mixed mode)
> Reporter: Mark Soderquist
>
> A message sent with the AMQP 1.0 native client interface is not consumable
> using an AMQP 1.0 JMS client. When we switched to sending the message with
> the JMS client the message was consumable by the JMS client. Are JMS style
> messages not compatible with AMQP style messages. Admittedly we assumed a
> message is a message on the broker and that we would be able to mix and match
> clients.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
