What I am seeing is that this XSL only checks the FIRST child node's (B)
attribute instead of checking all of them
XSLT 1.0 has a policy of never failing, so when you pass more than one
item to something that only expects one, it will use the first and
ignore the rest (this is sometimes called "First Item Semantics")
In this case you have:
//A[ contains(B/@a, "foo") ]
The element <A> has many <B> children, but the function contains() can
only take a single node so the first is used and the discarded,
effectively making your xpath:
//A[contains((B/@a[1]), 'foo')]
...which you know is wrong because you want to check all the child nodes.
XSLT 2.0 reversed this concept and will fail early, giving you a nice
error message instead of silently generating the wrong output.
--
Andrew Welch
http://andrewjwelch.com
Kernow: http://kernowforsaxon.sf.net/
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--