[
https://issues.apache.org/jira/browse/NIFI-1421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15116743#comment-15116743
]
ASF GitHub Bot commented on NIFI-1421:
--------------------------------------
GitHub user rpmiskin opened a pull request:
https://github.com/apache/nifi/pull/190
NIFI-1421 Make namespace ordering deterministic in SplitXML
Potential fix for Travis-CI test failure.
I'm using a TreeMap for the namespace prefixes, this will guarantee the
order that the namespaces are written out in the split file.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/rpmiskin/nifi NIFI-1421
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/190.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #190
----
commit c16c8db4594e977320a2fc8c29501ac40933ec87
Author: Richard Miskin <[email protected]>
Date: 2016-01-26T05:35:07Z
NIFI-1421 Make namespace ordering deterministic in SplitXML
----
> SplitXML produces invalid XML for source containing namespace declarations
> --------------------------------------------------------------------------
>
> Key: NIFI-1421
> URL: https://issues.apache.org/jira/browse/NIFI-1421
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 0.4.1
> Reporter: Richard Miskin
> Assignee: Joseph Witt
> Fix For: 0.5.0
>
> Attachments:
> 0001-NIFI-1421-This-closes-184.-Added-content-assertion-t.patch
>
>
> The SplitXML processor ignores namespace declarations which means the
> generated XML is invalid for examples like this:
> {code:xml}
> <?xml version="1.0" encoding="UTF-8"?>
> <bundle xmlns:foo="http://namespace/1">
> <node>
> <foo:subNode1 attribute="d&b">
> <value>Hello & Goodbye</value>
> </foo:subNode1>
> <foo:subNode2 xmlns:goo="http://namespace/2">
> <goo:value>World</goo:value>
> </foo:subNode2>
> </node>
> </bundle>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)