qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robbie Gemmell (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QPIDJMS-327) QPid JMS has no support for the content-type AMQP properties
Date Tue, 19 Dec 2017 17:56:00 GMT

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

Robbie Gemmell commented on QPIDJMS-327:

One of the reasons discussed for removing the content encoding related property was expectation
that for many uses cases seen for it, the client would be handling that itself and if couldn't
understand an encoding of a received message consider the message unprocessable. On the content
type, it needs to be seen how this interacts with existing usages of it by the client, and
also around how it should only be used with Data body sections. How the two aspects further
play into any message encryption efforts we would like to explore also needs to be considered.
These are all amongst the reasons the client does not yet support anything in this non-JMS
area and likely wont imminently.

> 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

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org

View raw message