You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2015/03/04 19:57:38 UTC
[jira] [Commented] (QPID-6432) [Java broker] [AMQP 1.0] add support
for mapping JMSType header to message Subject
[ https://issues.apache.org/jira/browse/QPID-6432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14347372#comment-14347372 ]
ASF subversion and git services commented on QPID-6432:
-------------------------------------------------------
Commit 1664114 from [~gemmellr] in branch 'qpid/trunk'
[ https://svn.apache.org/r1664114 ]
QPID-6432: when looking for the JMSType value use the message Subject first if present
> [Java broker] [AMQP 1.0] add support for mapping JMSType header to message Subject
> ----------------------------------------------------------------------------------
>
> Key: QPID-6432
> URL: https://issues.apache.org/jira/browse/QPID-6432
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: 0.31
> Reporter: Robbie Gemmell
> Assignee: Robbie Gemmell
> Fix For: 6.0 [Java]
>
>
> The JMS Mapping is going to define a mapping between the JMSType header and the Subject field of the AMQP message Properties section. The broker currently maps this using a message annotation used by the legacy JMS AMQP 1.0 client, we should update to support the Subject mapping as will be used by the new JMS client.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org