[QPIDJMS-52] support charset parameter in content-type value

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.1.0, 0.2.0
• Fix Version/s: 0.3.0
• Component/s: qpid-jms-client
• Assignee: Robbie Gemmell
• Reporter: Robbie Gemmell
• Created: 19/May/15 16:46
• Updated: 06/Jan/16 12:32
• Resolved: 20/May/15 13:29

Description

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.