qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QPIDJMS-21) Implement the JMS MapMessage interface
Date Fri, 16 May 2014 10:29:49 GMT

    [ https://issues.apache.org/jira/browse/QPIDJMS-21?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13998843#comment-13998843

ASF subversion and git services commented on QPIDJMS-21:

Commit 1594946 from [~gemmellr] in branch 'jms/trunk'
[ https://svn.apache.org/r1594946 ]

QPIDJMS-21, QPIDJMS-20: update the message type identification process

- Use the "x-opt-jms-msg-type" message annotation as the first means of
  identifying the JMS message type.
- Set the "x-opt-jms-msg-type" message annotation when creating new
  Message, MapMessage, ObjectMessage, BytesMessage instances. Others TBC.
- Interpret messages which contain an amqp-value section holding
  something other than Binary or null/String (e.g map or list) to be
  ObjectMessages if they omit the "x-opt-jms-msg-type" annotation.
- Change the message type annotation to a byte

> Implement the JMS MapMessage interface
> --------------------------------------
>                 Key: QPIDJMS-21
>                 URL: https://issues.apache.org/jira/browse/QPIDJMS-21
>             Project: Qpid JMS
>          Issue Type: New Feature
>            Reporter: Robbie Gemmell
>            Assignee: Robbie Gemmell
> Implement the JMS MapMessage interface

This message was sent by Atlassian JIRA

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

View raw message