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.