[
https://issues.apache.org/jira/browse/QPIDJMS-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14552317#comment-14552317
]
ASF subversion and git services commented on QPIDJMS-53:
--------------------------------------------------------
Commit 6b7320052b26fb2345bd3c7aac44e94857c98cbd in qpid-jms's branch
refs/heads/master from Robert Gemmell
[ https://git-wip-us.apache.org/repos/asf?p=qpid-jms.git;h=6b73200 ]
QPIDJMS-49, QPIDJMS-52, QPIDJMS-53: add some integration tests to verify the
pieces are wired up
> 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: [email protected]
For additional commands, e-mail: [email protected]
