The XSL file, below, should make $flights= {"1","2"}, but it contains
{"1"} -
when using the XML example file shown below.
xml-xalan CVS 11-Feb-02 9AM returns <out>1<br/></out> -sc
The question is whether the presence or absence of the first of these
successive colData elements
<colData colId="L">2</colData> <!-- If you delete this line it works -->
<colData colId="F">2</colData>
should affect
select="/report/colData[@colId='F' and not(.=preceding::colData)]
Per XPath 1.0 section 3.4, for equality expressions: "If both objects
to be compared are node-sets, then the comparison will be true if and
only if there is a node in the first node-set and a node in the second
node-set such that the result of performing the comparison on the
string-values of the two nodes is true."
XPath further says "The string-value of an element node is the
concatenation of the string-values of all text node descendants of the
element node in document order."
So the first colData be rejected by @colId="F" being false. And the
second should get false for not("2"="2") and the node should be rejected
for that reason.
"If you delete the first it works" -- well, if you delete the first then
the second is not rejected by that (not) test, and is accepted.
To my out-of-practice eye this appears to be Working As Designed.
Move to reject this issue and remove these files from tests/bugzilla.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org
For additional commands, e-mail: dev-h...@xalan.apache.org
