[
https://issues.apache.org/jira/browse/QPIDJMS-327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16266010#comment-16266010
]
Kai Hudalla commented on QPIDJMS-327:
-------------------------------------
Going through the latest docs published by the OASIS Advanced Message Queuing
Protocol (AMQP) Bindings and Mappings (AMQP-BINDMAP) TC on this subject, my
understanding is that the vendor property is (or will be)
{{JMS_AMQP_CONTENT_TYPE}}. However, the current QPID JMS Client 0.27 still
doesn't seem to support it, i.e. incoming messages do not have a String
property of that name which can be accessed via
{{javax.jms.Message.getStringProperty()}} and {{Message.getPropertyNames()}}
also doesn't seem to contain the property :-(
Is there any compelling reason why the content type is not (yet) mapped as
proposed in the JMS Binding document? I know that it hasn't been released yet.
However, FMPOV using the JMS client to interact with AMQP 1.0 infrastructure is
almost useless without a way to get/set the content-type.
> QPid JMS has no support for the content-type AMQP properties
> ------------------------------------------------------------
>
> Key: QPIDJMS-327
> URL: https://issues.apache.org/jira/browse/QPIDJMS-327
> Project: Qpid JMS
> Issue Type: Bug
> Components: qpid-jms-client
> Reporter: Leo Riguspi
>
> The content-type AMQP property cannot be set. According to the specifications
> it should be set via the Jms property JMS_AMQP_ContentType, however this
> results in nothing being set.
> NOTE: there is a similar issue (albeit different) for the content-encoding
> property (see [https://issues.apache.org/jira/browse/QPIDJMS-295])
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
