Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: [xsl] Can templates be invoked based on the value of a variable?

From: "pilgrim cnonline.net" <pilgrim@------------>
To:
Date: 4/2/2009 4:28:00 PM
Thanks, Michael L. & Lisa, the following worked well:

Given:
   <xsl:variable name="item" select="concat( 'item', $i)"/>

both
   <xsl:apply-templates select="*[ local-name() = $item ]"/>
and
   <xsl:apply-templates select="element()[ local-name() = $item ]"/>
worked fine.

Anyway,
a) I had missed the local-name() method, and name() wasn't doing any good.
b) I need more experience with XPath constructs, but at least I'm
getting better than I used to be!

I wanted to avoid the <xsl:choose/> construct since I have many more
than 2 possible "item" definitions to be processed.  Doable, but
bulky.  I have enough similar "item" templates as it is, which have
their own data to be processed by (thankfully) a common template.

New question:  Is there any execution efficiency advantage between
using "child::*"  or  "element()"?

Thanks again, Mike


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