[
https://issues.apache.org/jira/browse/CXF-7491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16260713#comment-16260713
]
ASF GitHub Bot commented on CXF-7491:
-------------------------------------
sberyozkin commented on issue #309: [CXF-7491] make Stax & XSLT interceptors
Charset-aware
URL: https://github.com/apache/cxf/pull/309#issuecomment-346025139
Np, sorry for a delay too. I see you check a message contextual property in
many places and if it is not set - default to UTF-8 and finally pass it as a
method parameter. What I suggested that, instead of updating all the methods
which need this encoding property - set it as a new Message property and get
the interceptors check the current Message. In fact, why don't interceptor
methods which need this encoding property simply check as in
https://github.com/apache/cxf/pull/309/files#diff-7b1f19d5162a1a32027e223ec72228eeR61
may be also have this code encapsulated in MessageUtils ?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> 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)
