Well. The 'other end' sends a long and and a string in a map message.
(from java sender)
jmsmessage.setBytes("name", "somestring".getBytes("UTF8"));
If the string contains for example 'abc', then everything works fine,
I can read the long and the string.
But if the string contains for example a greek zigma sign encoded
to utf, and put into the map message as bytes, then as soon as I read the
long, then boom! ??
Søren
Timothy Bish wrote:
>
> The C++ Client can only send and receive ASCII strings in Text Messages.
> To send Unicode strings your best bet is to encode them in a Bytes
> Message and decode them in your client code.
>
> To provide more insight it would be helpful if you could provide some
> sample code to show what exactly it is you are doing to encode and
> decode your data.
>
> Regards
> Tim.
>
> On Sun, 2008-10-05 at 11:41 -0700, Sodan wrote:
>> Hi there
>>
>> I am using the c++ client, and the mesage I am getting back have
>> different
>> members,
>> long, bytes etc.
>> The other end is trying to send me a message which contains a greek Zigma
>> sign, and he has encoded with UFT8 and done setbytes...
>> But when I do a read, not even on the bytes, but on the long I get:
>> OpenwireStringSupport::readString - Encoding not supported
>> FILE:
>> ..\src\main\activemq\connector\openwire\utils\OpenwireStringSupport.cpp,
>> LINE: 73
>>
>> huh?
>>
>> We want to be able to send back and forth UTF8 strings, and thought that
>> using bytes was the only way.
>> Any other good ideas ?
>>
>
>
>
--
View this message in context:
http://www.nabble.com/%27readString---Encoding-not-supported%27-exception-%28-ActiveMQ-CPP-%29-tp19827735p19835564.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
