[
https://issues.apache.org/jira/browse/NIFI-5567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16602764#comment-16602764
]
Christof Dilcher commented on NIFI-5567:
----------------------------------------
I have also used the suggestions made in
[this|http://mail-archives.us.apache.org/mod_mbox/nifi-users/201605.mbox/%3ccaev8zdx5vdozhyani_pb1mlgpma4ddsenczwd62k1qkn8ag...@mail.gmail.com%3E]
email thread.
This works but the notation is a little awkward and not very convenient to use.
An approach to namespaces that is more mainstream would be welcome.
> EvaluateXPath processor produces empty string sets for valid XPaths
> -------------------------------------------------------------------
>
> Key: NIFI-5567
> URL: https://issues.apache.org/jira/browse/NIFI-5567
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Affects Versions: 1.7.1
> Reporter: Christof Dilcher
> Priority: Major
> Labels: XPath, xml
> Attachments: EvaluateXPath_ExampleXML_empty_string_set.xml,
> EvaluateXPath_FlowFile_Attributes_empty_string_set.png,
> EvaluateXPath_ProcessorConfiguration_empty_string_set.png,
> EvaluateXPath_Template.png, EvaluateXPath_Template_empty_string_set.xml,
> EvaluateXPath_Test_template.xml
>
>
> I have found that valid XPath expressions apparently produce empty strings in
> EvaluateXPath processor which can be observed in the attached screenshots. I
> am using nifi 1.7.1 and jdk1.8.0_181.jdk. Any help would be appreciated!
> The source of the XML files is a GetFile Processor or a GenrateFlowFile
> Processor.
> I have also tested it with an InvokeHTTP processor where it works fine.
> However this does not solve it for me as I am dealing with physical XML files
> here. However this little detail might be interesting for the error finding
> process.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
