John,
"Great minds think alike", or so they say :>.
I'll pick this up and incorporate on the weekend if you have no objections?
I'd totally forgotten the ::intersect() method in the nodelist class.
Makes the code nice and neat and the change very simple. The method was
put in for XPath-Filter
I do my best thinking while driving home. Last night I thought that a possible
solution that I could try is exactly what you suggest below. So, I had another
look at the code today and tried the following code changes to
TXFMXPath::evaluateExpr(...) which seems to work (on the limited test data
John,
I think you've hit a bug. The Spec requires that the input to the XPath
transform be a node set - which implies that what you are doing is legal.
The C++ library assumes that the input is a document. Which means that
what you are doing will fail.
I just had a look at the Java library.
I dont know if this is legal XML DSIG but I tried to create one Reference that
contained multiple XPath Transforms, as below (note: both Transforms are the
same in this example, but I an really interested in a complex sequence of them):
http://www.w3.org/TR/1999/REC-xpath-19991116";>
h
