[
https://issues.apache.org/jira/browse/QPID-7280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15300717#comment-15300717
]
Rob Godfrey commented on QPID-7280:
-----------------------------------
Hi [~jflemer],
so the document is clearly wrong in equating mp.content_type with JMSType. The
content_type is used by the JMS client to identify the "type" of the message
(BytesMessage, TextMessage, MapMessage, etc...) since it describes the nature
of the encoding of the message body... so it cannot really be set independently
through the JMS client API (though it would be nice to allow TextMessages to
set the content type to be text/<something> and BytesMessages to be <anything
but text or amqp>/<something>), and obviously it is not great that there is no
way to get at the value of content type on the incoming message.
Were there other inaccuracies that you found?
> [Java 0-10 Client] [Documentation] Section 3.1 Java JMS Message Properties is
> incorrect
> ---------------------------------------------------------------------------------------
>
> Key: QPID-7280
> URL: https://issues.apache.org/jira/browse/QPID-7280
> Project: Qpid
> Issue Type: Bug
> Components: Documentation, Java Client
> Reporter: Rob Godfrey
>
> As noted by [~jflemer] in
> [this|https://issues.apache.org/jira/browse/QPID-4992?focusedCommentId=15300427&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15300427]
> comment on QPID-4992 , the documentation regarding the mapping of the
> message_properties.content_type field is incorrect
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
