You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Michael Fryars (JIRA)" <ji...@apache.org> on 2009/08/19 08:40:14 UTC
[jira] Updated: (AXIS2-4468) Failure to ISO-8559-1 encode server
response message body
[ https://issues.apache.org/jira/browse/AXIS2-4468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Fryars updated AXIS2-4468:
----------------------------------
Attachment: exp02_iso-8859-1.txt
exp01_utf8.txt
MfrTestService.aar
Attachments:
1) test AAR
2) debug trace of a UTF-8 request/response
3) debug trace of an ISO-8859-1 request/response
> Failure to ISO-8559-1 encode server response message body
> ---------------------------------------------------------
>
> Key: AXIS2-4468
> URL: https://issues.apache.org/jira/browse/AXIS2-4468
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: databinding
> Affects Versions: 1.5
> Environment: Axis2-1.5 / Tomcat 6.0 / XmlBeans
> Reporter: Michael Fryars
> Attachments: exp01_utf8.txt, exp02_iso-8859-1.txt, MfrTestService.aar
>
>
> 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
> ----------
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.