The internal transport representation for javax.jms.TextMessage is UTF. If you have captured the character data from the socket, which is what I assume you are using for talking with your C++ app, verify that you are constructing the string correctly.
| Socket s; | byte b[] = new byte[1000]; | s.getInputStream().read(b, 0, 1000); | String str = new String(b, "big5"); | In other words, probably not a JMS bug. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3843033#3843033 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3843033 ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
