Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@ws.apache.org
Message-ID: <537135.1162392654375.JavaMail.root@brutus>
Date: Wed, 1 Nov 2006 06:50:54 -0800 (PST)
From: "Bruno Negrao (JIRA)" <jira@apache.org>
To: axis-dev@ws.apache.org
Subject: [jira] Created: (AXIS2-1575) Axis2 does not decodes SOAP responses
 using the character encoding set on the response's XML declaration. Problem
 converting from iso-8859-1 to utf-8.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Axis2 does not decodes SOAP responses using the character encoding set on t=
he response's XML declaration. Problem converting from iso-8859-1 to utf-8.
---------------------------------------------------------------------------=
---------------------------------------------------------------------------

                 Key: AXIS2-1575
                 URL: http://issues.apache.org/jira/browse/AXIS2-1575
             Project: Apache Axis 2.0 (Axis2)
          Issue Type: Improvement
    Affects Versions: 1.0
         Environment: Windows XP + java 1.5 + axis2 1.0. I'm using client-s=
ide axis2 code. no server-side axis is involved.
            Reporter: Bruno Negrao
            Priority: Blocker


My SOAP server (it isn't axis2 based) sends SOAP responses like this one sh=
own at the end of this message.

The soap server does not set the 'Content-type' http header as was expected=
 so it's not possible to get the charset used in the response body from tha=
t.

But the server defines the character encoding  on the response's XML declar=
ation, example:=20
<?xml version=3D"1.0" encoding=3D"iso-8859-1"?>

Axis2 is ignoring the character enconding defining on the XML declaration a=
nd is decoding all the strings sent as if they were UTF-8.

The result is I cannot display the words correctly here on the client-side.=
 The OMElement.getText() method returns crazy utf-8 characters instead of m=
y latin characters (like =C3=A1 =C3=B3 =C3=A7 =C3=A3 =C3=AA, etc).

I proved that axis2 uses utf-8 to decode the network inputstream when I ran=
 the following method on the OMElement returned as response:

        response.getXMLStreamReader().getCharacterEncodingScheme()

It returns 'utf-8'  and it should return 'iso-8859-1'. Not only it returns =
utf-8 but it is indeed using utf-8 to decode the inputstream, what is wrong=
 for this situation.

The improvement I'm asking here is update axis2 so it obey to the encoding =
definition on the response's XML declaration.

thank you,

bruno.

***************************************************************************=
*************
AN EXAMPLE OF A SOAP RESPONSE SENT FROM MY SOAP SERVER:
***************************************************************************=
*************

HTTP/1.0 200 OK
Content-length: 1269

<?xml version=3D"1.0" encoding=3D"iso-8859-1"?>
   <soap:Envelope xmlns:soap=3D"http://schemas.xmlsoap.org/soap/envelope/">=
  =20
      <soap:Body>      =20
         <AgendaPesquisa>          =20
            <status>0</status>          =20
            <ListaContatosPesquisa>              =20
               <tipo>C</tipo>              =20
               <dono>lucia</dono>              =20
               <posicao>177</posicao>              =20
               <nome>Abric=C3=B3 Gimar=C3=A3es</nome>
               <email></email>          =20
            </ListaContatosPesquisa>      =20
         </AgendaPesquisa>  =20
      </soap:Body>
   </soap:Envelope>

--=20
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: htt=
p://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org