Uploaded image for project: 'Axis2'
  1. Axis2
  2. AXIS2-4468

Failure to ISO-8559-1 encode server response message body

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 1.5
    • 1.6.0
    • databinding
    • None
    • Axis2-1.5 / Tomcat 6.0 / XmlBeans

    Description

      When request has Content-Type: text/xml;charset=UTF-8, the response is labelled as UTF-8 and any special characters are correctly encoded in UTF-8.

      But when request has Content-Type: text/xml;charset=iso-8859-1, the response is labelled as ISO-8859-1 but the message body is still encoded as UTF-8.

      See thread at http://marc.info/?l=axis-user&m=125062671421564&w=2 for more details.
      ----------
      List: axis-user
      Subject: Re: [AXIS2] Control character encoding used by axis2 server for
      From: Andreas Veithen <andreas.veithen () gmail ! com>
      Date: 2009-08-18 20:17:40
      Message-ID: b67458760908181317v352bd106wd8fc9ae171728cc3 () mail ! gmail ! com
      [Download message RAW]

      Michael,

      The following log message is interesting:

      org.apache.axiom.om.impl.MTOMXMLStreamWriter - Returning access to
      the original output stream: java.io.BufferedOutputStream@14181418

      It means that the xmlbeans databinding bypasses the normal StAX
      XMLStreamWriter and writes part of the output directly to the
      underlying byte stream. It is probably at that moment that things go
      wrong. Can you please open a JIRA [1] and attach a sample AAR (or WAR)
      that allows us to reproduce this problem?

      Andreas
      ----------

      Attachments

        1. exp01_utf8.txt
          26 kB
          Michael Fryars
        2. exp02_iso-8859-1.txt
          26 kB
          Michael Fryars
        3. MfrTestService.aar
          563 kB
          Michael Fryars

        Activity

          People

            veithen Andreas Veithen
            mfryars Michael Fryars
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: