MQSeries.net :: View topic - JMS incoming Text Message and charset conversion

rsinha · Posted: Wed May 12, 2004 1:23 pm Post subject:

Hi, According to the JMS doc -

TextMessage
is an encoded string. For an outgoing message, the string is encoded in the character set given by the destination object. This defaults to UTF8 encoding (the UTF8 encoding starts with the first character of the message; there is no length field at the start). It is, however, possible to specify any other character set supported by WebSphere MQ Java. Such character sets are used mainly when you send a message to a non-JMS application.
If the character set is a double-byte set (including UTF16), the destination object's integer encoding specification determines the order of the bytes.

[size=18]An incoming message is interpreted using the character set and encoding that are specified in the message itself. These specifications are in the last WebSphere MQ header (or MQMD if there are no headers). For JMS messages, the last header is usually the MQRFH2. [/size]

I, however tried sending a Text Message using utf-8 encoding. At the oter end, first I read it using another JMS application, which gave me certain total byte count. Then, before reading the incoming message, I set setCCSID(int x) on Destination object to iso-8859-1. I was under the impression that I wouldn't see any change in behaviour this time as JMS will still interpret the message as utf-8, which is what the message was sent as by sending application.
But, after setting the ccsid to iso-8859-1 and then reading the message, when I took the total byte count, it was different then when I wasn't setting the ccsid to anything in the receiving application.

Can someone explain what's going on?

Thanx