Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: [xsl] xslt 1.0 vs xslt 2.0 problem

From: "Andrew Welch" <andrew.j.welch@--------->
To:
Date: 9/3/2008 5:43:00 PM
> 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/


transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent