[Feature Request] Add XPath 2.0 support for XML response filtering
See original GitHub issueFiltering XML responses with current XPath 1.0 is total pain when lot of namespaces and default namespaces are present (i.e. VMWave API). Simple things like finding some element required ugly //*[local-name() = 'tagName' ]
expressions.
XPath 2.0 will allow much simpler expressions, you can use this module for upgrade.
I tried to do it myself, but haven’t succeeded in building project, so it might be very helpful if someone could provide proper Dockerfile for app development and building.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:3
- Comments:18 (4 by maintainers)
Top Results From Across the Web
XForms 2.0: XPath expression module - W3C
This document is a module designed to add support for XPath as an expression language in XForms. XPath 2.0 is an expression language...
Read more >XSLT <xsl:for-each> Element - W3Schools
An XPath expression works like navigating a file system; where a forward slash (/) selects subdirectories. Filtering the Output. We can also filter...
Read more >Communicating with a WFS service in a web browser
The Filter parameter can be used in WFS requests to obtain specific features in a WFS service. The benefit of the Filter parameter...
Read more >Component Reference - Apache JMeter - User's Manual
Response Assertion; Duration Assertion; Size Assertion; XML Assertion ... Or, instead of manually adding HTTP Requests, you may want to use JMeter's HTTP(S) ......
Read more >ISO 19143:2010(en), Geographic information — Filter encoding
This International Standard describes an XML and KVP encoding of a system neutral syntax for expressing projections, selection and sorting clauses collectively ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Essentially the current filtering is useless for any SOAP responses, likely a common reason us enterprise folks are working with XML.
Would love to see support updated.
I do hope this issue doesn’t get closed, as XPath 2.0 will provide much simpler filtering patterns.