cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Schneider (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CXF-1749) Quick Fix for JMS Encoding issue
Date Thu, 14 Aug 2008 21:01:45 GMT

    [ https://issues.apache.org/jira/browse/CXF-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12622697#action_12622697
] 

Christian Schneider commented on CXF-1749:
------------------------------------------

For the short term fix we have to find out which encoding the message uses. Is it safe to
read this encoding from the <?xml encoding=""?> ?  Or is the encoding always UTF-8?

> Quick Fix for JMS Encoding issue
> --------------------------------
>
>                 Key: CXF-1749
>                 URL: https://issues.apache.org/jira/browse/CXF-1749
>             Project: CXF
>          Issue Type: Bug
>          Components: Transports
>    Affects Versions: 2.1.2
>            Reporter: Christian Schneider
>             Fix For: 2.1.3
>
>
> 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.


Mime
View raw message