[
https://issues.apache.org/jira/browse/CXF-7491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16149551#comment-16149551
]
ASF GitHub Bot commented on CXF-7491:
-------------------------------------
GitHub user cchepelov opened a pull request:
https://github.com/apache/cxf/pull/309
[CXF-7491] Fork Stax & XSLT interceptors to make them Charset-aware
per https://issues.apache.org/jira/browse/CXF-7491
this implements "solution 3" described there; forking the Stax & XSLT
transform interceptors to make them charset-aware, not blind "always UTF-8" as
previously
+ updates the tests to cover for this
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/cchepelov/cxf cxf-7491_nonutf8-interceptor
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cxf/pull/309.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #309
----
commit 56dd9e31ff7b403191294592a3fa0bb73ce0c780
Author: Cyrille Chépélov <c...@transparencyrights.com>
Date: 2017-08-31T20:28:03Z
[CXF-7491] Fork Stax & XSLT interceptors to make them Charset-aware
----
> TransformInInterceptor / TransformOutInterceptor assume UTF-8, ignore
> header-provided character set
> ---------------------------------------------------------------------------------------------------
>
> Key: CXF-7491
> URL: https://issues.apache.org/jira/browse/CXF-7491
> Project: CXF
> Issue Type: Bug
> Components: Soap Binding
> Affects Versions: 3.1.11, 3.1.12
> Environment: client Linux/Java/CXF (actually scala using
> sbt-play-soap)
> server IBMi AS/400
> Reporter: Cyrille Chépélov
>
> When talking to a server using IBMi / RPG-based software and SOAP gateway:
> the returned SOAP message contains XML encoded as ISO-8859-1; the HTTP header
> do specify a content type of xml+soap with character set ISO-8859-1; however
> the XML message itself include no character set declaration.
> Due to discrepancies between the official WSDL for the SOAP message and the
> remote implementation, a couple transforms had to be deployed. This works
> fine as long as the exchanged messages actually conform to US-ASCII (no
> diacritics), but whenever any character encoded differently between
> ISO-8859-1 and UTF-8 is used, the TransformInInterceptor fails to parse the
> text, as the XMLStreamReader is built to expect UTF-8 and actually receives
> ISO-8859-1 input
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
