cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rodrigo Merino (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CXF-7058) Extra CDATA elements added on long CDATA payload
Date Wed, 14 Sep 2016 16:28:20 GMT

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

Rodrigo Merino commented on CXF-7058:
-------------------------------------

Created a PR (https://github.com/apache/cxf/pull/169) to allow passing a parameter to bypass
the issue.

> Extra CDATA elements added on long CDATA payload
> ------------------------------------------------
>
>                 Key: CXF-7058
>                 URL: https://issues.apache.org/jira/browse/CXF-7058
>             Project: CXF
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.7.18, 3.1.7
>         Environment: All
>            Reporter: Rodrigo Merino
>         Attachments: headerSoapReqLongCdata.xml
>
>
> When calling StaxUtils.copy() with a source xml that contains a long CDATA section, that
long CDATA is sent in chunks to the writer, with each chunk being wrapped in a CDATA independently.
> For instance, {code}<![CDATA[a..z]]>{code} in the source ends in the destination
as {code}<![CDATA[a.]]><![CDATA[.z]]>{code}
> This can be verified by running the test org.apache.cxf.staxutils.StaxUtilsTest.testCopy()
with the attached xml file (headerSoapReqLongCdata.xml).
> I reported this initially to woodstox (https://github.com/FasterXML/woodstox/issues/21
and https://github.com/FasterXML/woodstox/issues/22),, but from Tatu's last answer (https://github.com/FasterXML/woodstox/issues/22#issuecomment-246254486)
is is something that should be handled in CXF's StaxUtils.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message