[jira] [Commented] (QPIDJMS-20) implement ability to send/receive ObjectMessage values encoded using the AMQP type system instead of Object serialization

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

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

ASF subversion and git services commented on QPIDJMS-20:
--------------------------------------------------------

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

QPIDJMS-20: initial work on using AMQP type encoding for sent/received ObjectMessage

> 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: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org