[ http://issues.apache.org/jira/browse/AXIS-1815?page=comments#action_59233 ] Toshiyuki Kimura commented on AXIS-1815: ----------------------------------------
Ushio-san, Sounds like you're using ISO-2022-JP(JIS), Windows-31J(SJIS), EUC-JP(EUC) or something, neither UTF-8 nor UTF-16. Right ? You'd better use UTF-8 or UTF-16 in your Web Services. But, there's an important reminder. If you use UTF-8 code with the current Axis, you might meet a number of numeric character references -- such as "ようこそ". It means that it'll still not work fine for you. Hmm... Thanks, Toshi > tcpmon don't support mulit-byte encording > ----------------------------------------- > > Key: AXIS-1815 > URL: http://issues.apache.org/jira/browse/AXIS-1815 > Project: Axis > Type: Improvement > Versions: 1.2RC2 > Reporter: Tuyoshi Ushio > > I am a user of tcpmon(TCP Monitor) in Japan. > This tool is very cool. > but... when I use mulit-byte character in SOAP-Request/Response XML, > tcpmon don't work well.(ex. Kanji character can't be displayed.) > In my environment, I change the code like this. > #tcpmon.SocketRR.run() method line 761-769 > --------------------------------------------before > textArea.append( new String( tmpbuffer, 0, i2 ) ); > // Shift saved bytes to the beginning > for ( i = 0 ; i < saved ; i++ ) { > buffer[i] = buffer[bufferLen - saved + i]; > } > } > else { > textArea.append( new String( buffer, 0, len ) ); > } > ---------------------------------------------after > textArea.append( new String( tmpbuffer, 0, i2 , soapEncording) ); > ^^^^^^^^^^^^^ > // Shift saved bytes to the beginning > for ( i = 0 ; i < saved ; i++ ) { > buffer[i] = buffer[bufferLen - saved + i]; > } > } > else { > textArea.append( new String( buffer, 0, len , soapEncording) ); > ^^^^^^^^^^^^^ > } > -------------------------------------------------- > I think tcpmon should check xml encording attribute. > (ex. <?xml version="1.0" encoding="utf-8" standalone="yes"?>) > ^^^^^^^^^^^^^^^^ > bye. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
