You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However the broken expressions
"license_manager/ip"
"vendor/@id"
"@id"
Extract correct results in OmniXML and no results in reference tools
From the hindsight, the reference tools (that are normally used to debug and
settle the expressions), so they kind add invisible virtual "document-root)
node on top of it. While OmniXML works inside the node with the document.
But that is very confusing and unexpected.
I'd propose to add
XPathSelect(NodeList, expression) overload
and
XPathSelect(Node, expression, TreatAsDocument: boolean = false)
or XPathSelectAsDoc(Node, expression)
To make transplanting expressions from editors/debuggers into sources easier
Original issue reported on code.google.com by `[email protected]` on 10 Dec 2014 at 2:51
The text was updated successfully, but these errors were encountered:
I try to extract values using expressions like
"hasp/license_manager/ip"
"hasp/vendor/@id"
"hasp/@id"
Correct results returned by
No matches returned by OmniXML XPathSelect
However the broken expressions
"license_manager/ip"
"vendor/@id"
"@id"
Extract correct results in OmniXML and no results in reference tools
From the hindsight, the reference tools (that are normally used to debug and
settle the expressions), so they kind add invisible virtual "document-root)
node on top of it. While OmniXML works inside the node with the document.
But that is very confusing and unexpected.
I'd propose to add
XPathSelect(NodeList, expression) overload
and
XPathSelect(Node, expression, TreatAsDocument: boolean = false)
or XPathSelectAsDoc(Node, expression)
To make transplanting expressions from editors/debuggers into sources easier
The text was updated successfully, but these errors were encountered: