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 2015/05/19 18:56:59 UTC
[jira] [Created] (QPIDJMS-53) treat messages with a Data section
and common textual content-type values as TextMessage
Robbie Gemmell created QPIDJMS-53:
-------------------------------------
Summary: treat messages with a Data section and common textual content-type values as TextMessage
Key: QPIDJMS-53
URL: https://issues.apache.org/jira/browse/QPIDJMS-53
Project: Qpid JMS
Issue Type: Improvement
Components: qpid-jms-client
Affects Versions: 0.2.0
Reporter: Robbie Gemmell
Assignee: Robbie Gemmell
Fix For: 0.3.0
Previously, only an exact "text/plain" content-type would be treated as a TextMessage when receiving a message with a Data body section (and not annotated with the x-opt-jms-msg-type annotation). QPIDJMS-52 adds suport for the charset paramater.
The content-type should also be used to ensure other common textual types are treated as TextMessage rather than BytesMessage. Only messages with no content-type, 'application/octet-stream', malformed content-type, or some other unknown content-types would then be treated as BytesMessage.
Candidates include:
text/*
application/json
application/xml
application/xml-dtd
application/javascript
application/ecmascript
application/<something>+xml
application/<something>+json
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org