[jira] [Commented] (CXF-7491) TransformInInterceptor / TransformOutInterceptor assume UTF-8, ignore header-provided character set

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CXF-7491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16239827#comment-16239827 ] 

ASF GitHub Bot commented on CXF-7491:
-------------------------------------

cchepelov commented on issue #309: [CXF-7491] Fork Stax & XSLT interceptors to make them Charset-aware
URL: https://github.com/apache/cxf/pull/309#issuecomment-342029524
 
 
   @sberyozkin many apologies for not coming back earlier
   
   I've updated the PR to switch back to updating the protected methods, which bets hardly anyone extended the classes in question (+ some checkstyle tidying up)
   
   I'm not sure adding a message property would work, since the whole point of the patch is to read the existing property and add an "encoding" arguments to internal methods to pass it on, but I might misread.
   

----------------------------------------------------------------
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:
users@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)