You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@qpid.apache.org by "Robbie Gemmell (JIRA)" <ji...@apache.org> on 2015/08/12 16:28:45 UTC

[jira] [Resolved] (QPIDJMS-89) MapMessages that are not annotated as such, are handled as ObjectMessages by the consumer instead

     [ https://issues.apache.org/jira/browse/QPIDJMS-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robbie Gemmell resolved QPIDJMS-89.
-----------------------------------
    Resolution: Not A Problem

> MapMessages that are not annotated as such, are handled as ObjectMessages by the consumer instead
> -------------------------------------------------------------------------------------------------
>
>                 Key: QPIDJMS-89
>                 URL: https://issues.apache.org/jira/browse/QPIDJMS-89
>             Project: Qpid JMS
>          Issue Type: Bug
>          Components: qpid-jms-client
>    Affects Versions: 0.2.0, 0.3.0
>            Reporter: Alex Plischke
>              Labels: qpidclient
>         Attachments: 0001-QPIDJMS-89-Handle-unannoted-MapMessages-during-consu.patch
>
>
> If the annotation type "x-opt-jms-msg-type" is missing from the message (e.g. the message was created by the old qpid amqp 1.0 client) and this message is supposed to be a MapMessage, then the consumer will create an ObjectMessage instead.
> This is due to AmqpJmsMessageBuilder.createWithoutAnnotation() not handling the MapMessage case, which ends up creating an ObjectMessage instead.



--
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