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 2017/09/27 11:49:00 UTC
[jira] [Commented] (QPIDJMS-327) QPid JMS has no support for the
content-type AMQP properties
[ https://issues.apache.org/jira/browse/QPIDJMS-327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16182425#comment-16182425 ]
Robbie Gemmell commented on QPIDJMS-327:
----------------------------------------
Similar to QPIDJMS-295, JMS_AMQP_ContentType is also an ActiveMQ-specific extension, using an Application Property which the broker internally utilises when doing certain things such as converting messages between different protocols when using some of its 'transformers'. The Qpid JMS client does not specifically know about that property and does not map it to the content-type field of the AMQP message Properties section. Finalising behaviour around content type and encoding is an outstanding area of work, its a fairly complicated subject, but really sits entirely outwith JMS functionality.
> 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: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org