[
https://issues.apache.org/jira/browse/QPIDJMS-327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16285608#comment-16285608
]
Kai Hudalla commented on QPIDJMS-327:
-------------------------------------
Then FMPOV this is an even stronger argument for adding the properties to the
Qpid JMS provider right now, since there doesn't seem to be a need to
coordinate with the TC anymore, is there?
I can only encourage the inclusion of at least the JMS_AMQP_CONTENT_TYPE and
JMS_AMYP_CONTENT_ENCODING properties because FMPOV these are *very* useful for
application developers.
> 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-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
