activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Timothy Bish <tabish...@gmail.com>
Subject Re: Apache.NMS.Stomp error receiving special characters
Date Mon, 31 Jan 2011 21:36:53 GMT
On Mon, 2011-01-31 at 22:20 +0100, David Pascual wrote:
> Hi,
> 
> 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);
> 
> Wiht this modification, text messages with special characters are received
> without errors.
> 
> Do we have to do something to send special chareacters in a text message
> with Stom? Do you know if we can configure Stomp client to use
> Encodig.Default?
> 
> Thanks in advance
> David

The Stomp .NET client is expecting that the text in the body of the
message is encoded as UTF-8.  Is you text being encoded as UTF-8?

Regards

-- 
Tim Bish
------------
FuseSource
Email: tim.bish@fusesource.com
Web: http://fusesource.com
Twitter: tabish121
Blog: http://timbish.blogspot.com/



Mime
View raw message