[
https://issues.apache.org/jira/browse/QPIDJMS-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13998845#comment-13998845
]
ASF subversion and git services commented on QPIDJMS-20:
--------------------------------------------------------
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 ability to send/receive ObjectMessage values encoded using the AMQP
> type system instead of Object serialization
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: QPIDJMS-20
> URL: https://issues.apache.org/jira/browse/QPIDJMS-20
> Project: Qpid JMS
> Issue Type: New Feature
> Reporter: Robbie Gemmell
> Assignee: Robbie Gemmell
>
> ObjectMessage values are traditionally sent as serialized Java objects, with
> "application/x-java-serialized-object" content type. It would be useful to
> add functionality to send a particular ObjectMessage by encoding its content
> (e.g a List) using the AMQP type system instead, for improved
> interoperability with other AMQP 1.0 systems. The reverse functionality is
> useful for receiving arbitrary AMQP messages which may have content that cant
> be usefully conveyed though the other JMS Message interfaces.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
