You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Christian Schneider (JIRA)" <ji...@apache.org> on 2008/08/14 22:55:44 UTC
[jira] Created: (CXF-1749) Quick Fix for JMS Encoding issue
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.
[jira] Assigned: (CXF-1749) Quick Fix for JMS Encoding issue
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Willem Jiang reassigned CXF-1749:
---------------------------------
Assignee: Willem Jiang
> 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
> 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.
[jira] Commented: (CXF-1749) Quick Fix for JMS Encoding issue
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12643773#action_12643773 ]
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: https://issues.apache.org/jira/browse/CXF-1749
> 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.
[jira] Updated: (CXF-1749) Quick Fix for JMS Encoding issue
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Willem Jiang updated CXF-1749:
------------------------------
Fix Version/s: (was: 2.1.3)
2.1.4
> 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.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.
[jira] Commented: (CXF-1749) Quick Fix for JMS Encoding issue
Posted by "Christian Schneider (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Resolved: (CXF-1749) Quick Fix for JMS Encoding issue
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Willem Jiang resolved CXF-1749.
-------------------------------
Resolution: Fixed
Fix Version/s: 2.2
2.0.10
trunk: http://svn.apache.org/viewvc?rev=709353&view=rev
http://svn.apache.org/viewvc?rev=709354&view=rev
2.1.x: http://svn.apache.org/viewvc?rev=709357&view=rev
2.0.x: http://svn.apache.org/viewvc?rev=709363&view=rev
> 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
> Assignee: Willem Jiang
> Fix For: 2.0.10, 2.1.4, 2.2
>
>
> 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.