Xinjun, Folks, If someone can help recreate the problem, we will try to fix it for 1.1 release. Here's what we use to test UTF-16 switch
https://svn.apache.org/repos/asf/webservices/commons/trunk/modules/axiom/modules/axiom-tests/src/test/java/org/apache/axiom/soap/impl/llom/CharacterEncodingTest.java Please log a JIRA issue with an updated test to help us... thanks, dims On 11/1/06, Xinjun Chen <[EMAIL PROTECTED]> wrote:
Hi, I have the similar problem. I am using the Axis2 client, when the end service send RIGHT SINGLE QUOTATION MARK (U+2019, or 0xE2 0x80 0x99, or e28099). From Ethereal, I can see the bytes e2 80 99. However, Axis2 just convert it to question mark (0x3F). I am not sure whether it is also caused by this bug. I am going to rollout the project. Is there any estimated timeline for the resolve of this problem? Thank you. Regards, Xinjun On 11/1/06, Davanum Srinivas <[EMAIL PROTECTED] > wrote: > Bruno, > > Please log a JIRA bug with your sample. > > thanks, > dims > > On 11/1/06, Manuel Mall < [EMAIL PROTECTED]> wrote: > > On Wednesday 01 November 2006 13:43, Bruno Negrao wrote: > > > Bruno, > > > > > > encoding issues in my experience can be very tricky to debug. Never > > > rely on any characters you see on the screen or in print to figure > > > out the actual encoding used. The tool which displays / prints may > > > have weaved its own encoding/decoding 'magic' and may show you > > > distorted results. Look at the actual byte stream and check how the > > > characters are actually encoded in it, i.e. how does the message > > > appear 'on the wire'. > > > > > > Manuel > > > > > > > > > Manuel, > > > > > > I already tried my tests without tcpmon in the middle and the > > > problems persisted anyway. > > > > Bruno, > > > > you may well be correct that the problem is in Axis but to be sure I > > would recommend you use a 'proper' protocol analyser, e.g. Ethereal > > ( www.ethereal.com) worked well for me in the past when I needed to look > > at 'bytes on the wire'. > > > > Manuel > > > > > > But I'll check there on the server side if at least the words were > > > correctly stored as iso-8859-1. > > > > > > But this does not dismiss my observation about > > > response.getXMLStreamReader().getCharacterEncodingScheme() > > > > > > That method should definitely return "iso-8859-1" instead of "utf-8". > > > I believe this is a proof that axis2 is not doing what it was > > > supposed to. > > > > > > I'd ask you to carefully read my previous posting and analyze those > > > evidences I showed. > > > > > > Thank you, > > > bruno. > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers) > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
-- Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
