Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
From: gemmellr <git@git.apache.org>
To: dev@activemq.apache.org
Reply-To: dev@activemq.apache.org
References: <git-pr-1590-activemq-artemis@git.apache.org>
In-Reply-To: <git-pr-1590-activemq-artemis@git.apache.org>
Subject: [GitHub] activemq-artemis issue #1590: ARTEMIS-1464 Fix Core to AMQP conversion Bytes...
Content-Type: text/plain
Message-Id: <20171017100354.0091BDFAE3@git1-us-west.apache.org>
Date: Tue, 17 Oct 2017 10:03:53 +0000 (UTC)
archived-at: Tue, 17 Oct 2017 10:03:56 -0000

Github user gemmellr commented on the issue:

    https://github.com/apache/activemq-artemis/pull/1590
  
    The AMQP JMS mapping is in part around getting any different AMQP JMS implementations behaving consistently with each other, it could as easily say use amqp-value, or say use either. The JMS mapping/client also copes with receiving either, see the recieving side mapping details later in the doc.
    
    There is nothing wrong with the broker sending amqp-value sections, and other clients might prefer that. It seems entirely unrelated to the actual defect here, so I'd leave it the way it is, but even if it were changed I would actually separate it out as its own specific change. 


---