cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Willem Jiang (JIRA)" <>
Subject [jira] Commented: (CXF-1749) Quick Fix for JMS Encoding issue
Date Thu, 30 Oct 2008 07:44:44 GMT


Willem Jiang commented on CXF-1749:

I think we can leverage the content-type which holds the charset (encoding) information. 
If there is no charset information you use the default encoding UTF-8, otherwise we set the
message encoding to the charset.
BTW, there is Message.ENCODING  key in the Message , I think we need to use it to specify
the text message's encoding.

> Quick Fix for JMS Encoding issue
> --------------------------------
>                 Key: CXF-1749
>                 URL:
>             Project: CXF
>          Issue Type: Bug
>          Components: Transports
>    Affects Versions: 2.1.2
>            Reporter: Christian Schneider
>            Assignee: Willem Jiang
>             Fix For: 2.1.4
> The encoding of JMS Messages is wrong if they are sent as TextMessage and the platform
encoding is not equal to the message encoding. This issue is linked to CXF-1668. While the
other issue handles a long term solution like proposed from Daniel Kulp this issue aims to
provide a short term fix.
> The short term fix is to avoid the simple getBytes() call and instead call getBytes(<encoding>)
with the correct encoding.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message