[
https://issues.apache.org/jira/browse/CXF-7491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16156768#comment-16156768
]
ASF GitHub Bot commented on CXF-7491:
-------------------------------------
Github user sberyozkin commented on the issue:
https://github.com/apache/cxf/pull/309
I'm not sure if users actually have ever tried to extend these classes, we
can ask at the CXF users for example if someone has tried it...Can you please
try to do another PR but based on updating the protected methods, or may be you
can find a way to pass that extra parameter as a new message property, example,
Message.PAYLOAD_ENCODING, or similar ? thanks
> 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)
