[
https://issues.apache.org/jira/browse/QPIDJMS-52?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14550773#comment-14550773
]
ASF subversion and git services commented on QPIDJMS-52:
--------------------------------------------------------
Commit 021867fd17f835f3d665f35d3b94abd6d51c9f5c in qpid-jms's branch
refs/heads/master from Robert Gemmell
[ https://git-wip-us.apache.org/repos/asf?p=qpid-jms.git;h=021867f ]
QPIDJMS-52, QPIDJMS-53: support the charset param in content-type, and treat
messages with Data sections and common textual content-types as TextMessage
rahter than BytesMessage
> support charset parameter in content-type value
> -----------------------------------------------
>
> Key: QPIDJMS-52
> URL: https://issues.apache.org/jira/browse/QPIDJMS-52
> Project: Qpid JMS
> Issue Type: Bug
> Components: qpid-jms-client
> Affects Versions: 0.2.0
> Reporter: Robbie Gemmell
> Assignee: Robbie Gemmell
> Fix For: 0.3.0
>
>
> Currently when a message arrives that is not annotated with the
> 'x-opt-jms-msg-type' annotation the client tags is messages with, if the
> message has a Data Data section and a 'text/plain' content-type then it will
> be treated as a TextMessage. However, this would instead be treated as a
> BytesMessage currently if the content-type contains a charset parameter, e.g
> 'text/plain;charset=utf-8'.
> Add support for the charset param to identify the character set used and
> prevent treating these messages as BytesMessages.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
