You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Pierre Villard (Jira)" <ji...@apache.org> on 2026/01/05 10:36:07 UTC

[jira] [Resolved] (NIFI-5144) TransformXml crashes creating CDATA (Saxon issue?)

     [ https://issues.apache.org/jira/browse/NIFI-5144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pierre Villard resolved NIFI-5144.
----------------------------------
    Resolution: Feedback Received

Apache NiFi 1.x is no longer maintained and no new release is planned on the 1.x release line. Marking as resolved as part of a cleanup operation. Please open a new one with an updated description if this is still relevant for NiFi 2.x.

> TransformXml crashes creating CDATA (Saxon issue?)
> --------------------------------------------------
>
>                 Key: NIFI-5144
>                 URL: https://issues.apache.org/jira/browse/NIFI-5144
>             Project: Apache NiFi
>          Issue Type: Bug
>    Affects Versions: 1.6.0
>            Reporter: Chris Green
>            Priority: Major
>              Labels: Processor, TransformXml
>         Attachments: trace.txt
>
>
> Hi all,
> I've not submitted a Jira issue before, apologies if this is in the wrong place.
>  
> I'm attempting to transform XML containing CDATA sections, into another structure but keeping the CDATA tags. A 3rd party XML transformer confirms the XSLT I've got transforms the XML successfully, using xsl:output to specify which output elements to create as CDATA.
> Using the same XML and XSLT in NiFi 1.6.0 causes the following exception:
>  
> {quote}java.lang.IllegalArgumentException: Value of \{cdata-section-elements} must be a list of QNames in '\{uri}local' notation{quote}
>  
> The stack trace (attached) mentions the Saxon library, which I've searched for along with the exception and found the bug detailed [here|https://saxonica.plan.io/issues/2795].
> NiFi 1.6.0 appears to be bundled with Saxon-HE-9.6.0-5.jar, which is a version from before the bug above was fixed (if they are related).
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)