activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Pascual (JIRA)" <jira+amq...@apache.org>
Subject [jira] Updated: (AMQNET-315) Error receiving special characters
Date Tue, 01 Feb 2011 12:12:29 GMT

     [ 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

       

Mime
View raw message