Any advice on this please? -------- Original Message -------- Subject: [Axis2] Axis2 client generated from WSDL ignoring encoding Date: Thu, 23 Feb 2012 17:02:42 +0000 From: Francisco Serrano <francisco.serr...@multicom.co.uk> To: java-user@axis.apache.org
Hello, I have an axis2 client generated from a WSDL, which is working fine but I'm having some problems since it's ignoring the charset specified in the response it's getting back. The response specifies charset=UTF-8 in the Content-Type HTTP header and the same in the encoding parameter in the xml message. Instead of using UTF-8 to decode the xml content, it's using ISO-8859-1 which is the one set for the JVM where the client is running. For this reason I'm getting some strange characters in the response. I've double checked that the characters are encoded correctly using UTF-8. It's an old client generated with version 1.0. Does anybody know if there's some issue about that version regarding this problem? Are there any parameters to specify the charset to use to decode the response? Best regards, Francisco. -- Multicom Products Limited is a company registered in England and Wales (Registered Number 2447353 Wales) with its registered office at 33 Victoria Street, Bristol, BS1 6AS. This email is confidential to the addressee and may contain privileged information. If you have reason to believe that you are not the intended recipient of this communication, please delete it from your system and contact the sender immediately. You are not permitted to use or copy this email or its attachments nor may you disclose the same to any third party. Unauthorised use or disclosure of this email is prohibited and may be unlawful. We reserve the right to intercept and read emails sent or received by our employees. This is to ensure compliance with our internal policies and to protect our business. If you do not wish for your communications to be subjected to such scrutiny, you should not communicate via this email system. We endeavour to exclude viruses and other malware from our data but it is the responsibility of the recipient to scan all emails and attachments for viruses before opening them. We accept no liability for any damage caused by any virus transmitted by this email. Email may not be completely secure or error free, can be intercepted or corrupted and may arrive late or not at all. Anyone who communicates with us by email accepts these risks.
