Dear all,
first of all, thanks for Jaxen and Saxpath. Good XPath implementations
are rare, and my benchmarks indicate that Jaxen is up to 10 times faster
than Xalan, so Jaxen qualifies as 'good' :)
However, there seems to be a problem with your predicate evaluation.
Here's a sample XML document for recreating the problem.
<?xml version='1.0'?>
<foo>
<bar>
<baz/>
<baz/>
<baz/>
</bar>
<bar>
<baz/>
<baz/>
<baz/>
</bar>
</foo>
If you execute "/foo/bar/baz[1]" on this document, Jaxen returns a list
of size 1, presumably containing the very first "baz". The correct
behavior should be to return a list containing the first baz in the
first bar and the first baz in the second bar, i.e. a list of size 2.
I suspect that Jaxen filters its nodes at the very end after retrieving
all nodes into a list, instead of filtering the nodes collected at every
step?
Christian
_______________________________________________
Jaxen-interest mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jaxen-interest
