You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "David Pascual (JIRA)" <ji...@apache.org> on 2011/02/01 13:08:28 UTC
[jira] Created: (AMQNET-315) Error receiving special characters
Error receiving special characters
----------------------------------
Key: AMQNET-315
URL: https://issues.apache.org/jira/browse/AMQNET-315
Project: ActiveMQ .Net
Issue Type: Bug
Components: Stomp
Affects Versions: 1.4.1
Environment: tested in net-2.0 and netcf-2.0
Reporter: David Pascual
Assignee: Jim Gomes
We are using NMS STOMP client for CF 2.0, and we have a error when the client recives text messages with special characters like "é", that are transformed in illegible characters.
I have modified the BinaryReader constructor from "TcpTransport" class in NMS Stomp client, just to add Encoding.Default (instead of to use UTF-8, that is use for default constructor)
socketReader = new BinaryReader(CreateSocketStream(), Encoding.Default);
With this modification, text messages with special characters are received without errors.
Test that demonstrates the issue attached.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQNET-315) Error receiving special characters
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQNET-315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish updated AMQNET-315:
--------------------------------
Fix Version/s: 1.5.2
> Error receiving special characters
> ----------------------------------
>
> Key: AMQNET-315
> URL: https://issues.apache.org/jira/browse/AMQNET-315
> Project: ActiveMQ .Net
> Issue Type: Bug
> Components: Stomp
> Affects Versions: 1.4.0, 1.5.0, 1.5.1
> Environment: tested in net-2.0 and netcf-2.0
> Reporter: David Pascual
> Assignee: Timothy Bish
> Fix For: 1.5.2, 1.6.0
>
> Attachments: SpecialCharactersTest.cs
>
>
> We are using NMS STOMP client for CF 2.0, and we have a error when the client recives text messages with special characters like "é", that are transformed in illegible characters.
> I have modified the BinaryReader constructor from "TcpTransport" class in NMS Stomp client, just to add Encoding.Default (instead of to use UTF-8, that is use for default constructor)
> socketReader = new BinaryReader(CreateSocketStream(), Encoding.Default);
> With this modification, text messages with special characters are received without errors.
> Test that demonstrates the issue attached.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQNET-315) Error receiving special characters
Posted by "David Pascual (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQNET-315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Pascual updated AMQNET-315:
---------------------------------
Attachment: SpecialCharactersTest.cs
> Error receiving special characters
> ----------------------------------
>
> Key: AMQNET-315
> URL: https://issues.apache.org/jira/browse/AMQNET-315
> Project: ActiveMQ .Net
> Issue Type: Bug
> Components: Stomp
> Affects Versions: 1.4.1
> Environment: tested in net-2.0 and netcf-2.0
> Reporter: David Pascual
> Assignee: Jim Gomes
> Attachments: SpecialCharactersTest.cs
>
>
> We are using NMS STOMP client for CF 2.0, and we have a error when the client recives text messages with special characters like "é", that are transformed in illegible characters.
> I have modified the BinaryReader constructor from "TcpTransport" class in NMS Stomp client, just to add Encoding.Default (instead of to use UTF-8, that is use for default constructor)
> socketReader = new BinaryReader(CreateSocketStream(), Encoding.Default);
> With this modification, text messages with special characters are received without errors.
> Test that demonstrates the issue attached.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (AMQNET-315) Error receiving special characters
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQNET-315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish reassigned AMQNET-315:
-----------------------------------
Assignee: Timothy Bish (was: Jim Gomes)
> Error receiving special characters
> ----------------------------------
>
> Key: AMQNET-315
> URL: https://issues.apache.org/jira/browse/AMQNET-315
> Project: ActiveMQ .Net
> Issue Type: Bug
> Components: Stomp
> Affects Versions: 1.4.0, 1.5.0, 1.5.1
> Environment: tested in net-2.0 and netcf-2.0
> Reporter: David Pascual
> Assignee: Timothy Bish
> Attachments: SpecialCharactersTest.cs
>
>
> We are using NMS STOMP client for CF 2.0, and we have a error when the client recives text messages with special characters like "é", that are transformed in illegible characters.
> I have modified the BinaryReader constructor from "TcpTransport" class in NMS Stomp client, just to add Encoding.Default (instead of to use UTF-8, that is use for default constructor)
> socketReader = new BinaryReader(CreateSocketStream(), Encoding.Default);
> With this modification, text messages with special characters are received without errors.
> Test that demonstrates the issue attached.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQNET-315) Error receiving special characters
Posted by "David Pascual (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQNET-315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Pascual updated AMQNET-315:
---------------------------------
Affects Version/s: 1.5.0
1.4.0
> Error receiving special characters
> ----------------------------------
>
> Key: AMQNET-315
> URL: https://issues.apache.org/jira/browse/AMQNET-315
> Project: ActiveMQ .Net
> Issue Type: Bug
> Components: Stomp
> Affects Versions: 1.4.0, 1.5.0, 1.5.1
> Environment: tested in net-2.0 and netcf-2.0
> Reporter: David Pascual
> Assignee: Jim Gomes
> Attachments: SpecialCharactersTest.cs
>
>
> We are using NMS STOMP client for CF 2.0, and we have a error when the client recives text messages with special characters like "é", that are transformed in illegible characters.
> I have modified the BinaryReader constructor from "TcpTransport" class in NMS Stomp client, just to add Encoding.Default (instead of to use UTF-8, that is use for default constructor)
> socketReader = new BinaryReader(CreateSocketStream(), Encoding.Default);
> With this modification, text messages with special characters are received without errors.
> Test that demonstrates the issue attached.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (AMQNET-315) Error receiving special characters
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQNET-315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish resolved AMQNET-315.
---------------------------------
Resolution: Fixed
Fix Version/s: 1.6.0
> Error receiving special characters
> ----------------------------------
>
> Key: AMQNET-315
> URL: https://issues.apache.org/jira/browse/AMQNET-315
> Project: ActiveMQ .Net
> Issue Type: Bug
> Components: Stomp
> Affects Versions: 1.4.0, 1.5.0, 1.5.1
> Environment: tested in net-2.0 and netcf-2.0
> Reporter: David Pascual
> Assignee: Timothy Bish
> Fix For: 1.6.0
>
> Attachments: SpecialCharactersTest.cs
>
>
> We are using NMS STOMP client for CF 2.0, and we have a error when the client recives text messages with special characters like "é", that are transformed in illegible characters.
> I have modified the BinaryReader constructor from "TcpTransport" class in NMS Stomp client, just to add Encoding.Default (instead of to use UTF-8, that is use for default constructor)
> socketReader = new BinaryReader(CreateSocketStream(), Encoding.Default);
> With this modification, text messages with special characters are received without errors.
> Test that demonstrates the issue attached.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (AMQNET-315) Error receiving special characters
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQNET-315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12991239#comment-12991239 ]
Timothy Bish commented on AMQNET-315:
-------------------------------------
Fixed in trunk and 1.5.x fixes branch.
> Error receiving special characters
> ----------------------------------
>
> Key: AMQNET-315
> URL: https://issues.apache.org/jira/browse/AMQNET-315
> Project: ActiveMQ .Net
> Issue Type: Bug
> Components: Stomp
> Affects Versions: 1.4.0, 1.5.0, 1.5.1
> Environment: tested in net-2.0 and netcf-2.0
> Reporter: David Pascual
> Assignee: Timothy Bish
> Fix For: 1.6.0
>
> Attachments: SpecialCharactersTest.cs
>
>
> We are using NMS STOMP client for CF 2.0, and we have a error when the client recives text messages with special characters like "é", that are transformed in illegible characters.
> I have modified the BinaryReader constructor from "TcpTransport" class in NMS Stomp client, just to add Encoding.Default (instead of to use UTF-8, that is use for default constructor)
> socketReader = new BinaryReader(CreateSocketStream(), Encoding.Default);
> With this modification, text messages with special characters are received without errors.
> Test that demonstrates the issue attached.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQNET-315) Error receiving special characters
Posted by "David Pascual (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQNET-315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Pascual updated AMQNET-315:
---------------------------------
Affects Version/s: (was: 1.4.1)
1.5.1
> Error receiving special characters
> ----------------------------------
>
> Key: AMQNET-315
> URL: https://issues.apache.org/jira/browse/AMQNET-315
> Project: ActiveMQ .Net
> Issue Type: Bug
> Components: Stomp
> Affects Versions: 1.4.0, 1.5.0, 1.5.1
> Environment: tested in net-2.0 and netcf-2.0
> Reporter: David Pascual
> Assignee: Jim Gomes
> Attachments: SpecialCharactersTest.cs
>
>
> We are using NMS STOMP client for CF 2.0, and we have a error when the client recives text messages with special characters like "é", that are transformed in illegible characters.
> I have modified the BinaryReader constructor from "TcpTransport" class in NMS Stomp client, just to add Encoding.Default (instead of to use UTF-8, that is use for default constructor)
> socketReader = new BinaryReader(CreateSocketStream(), Encoding.Default);
> With this modification, text messages with special characters are received without errors.
> Test that demonstrates the issue attached.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira