[XSL-LIST Mailing List Archive Home]
[By Thread]
[By Date]
I think I've got it with a for-each loop:
<xsl:param name="schema" select="document(//@xsi:noNamespaceSchemaLocation)/*"/>
<xsl:for-each select="$schema">
<xsl:apply-templates select="saxon:evaluate($xsd-path)"/> </xsl:for-each>
But, I feel a little wierd about using for-each like this. Seems like there should be a way to do this without running the risk of having the "for loop" and the possibiliy of my apply templates getting called more than once.
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Re: [xsl] On the XPath to my editor....
Subject: Re: [xsl] On the XPath to my editor.... From: "Mark R. Diggory" <mdiggory@xxxxxxxxxxxxxxxxx> Date: Thu, 16 May 2002 22:20:39 -0400 |
Example: <xsl:param name="xsd-path">/xs:schema[1]/xs:element[5]</xsl:param> <xsl:param name="schema" select="document('loc_of_schema')"/>
<xsl:apply-templates select="$schema/*[saxon:evaluate($xsd-path)]"/> ...
But what I end up getting is all the child elements of the xs:schema element.
I think I've got it with a for-each loop:
<xsl:param name="schema" select="document(//@xsi:noNamespaceSchemaLocation)/*"/>
<xsl:for-each select="$schema">
<xsl:apply-templates select="saxon:evaluate($xsd-path)"/> </xsl:for-each>
But, I feel a little wierd about using for-each like this. Seems like there should be a way to do this without running the risk of having the "for loop" and the possibiliy of my apply templates getting called more than once.
-Thanks, Mark
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
[xsl] On the XPath to my editor...., Mark R. Diggory | Thread | Re: [xsl] On the XPath to my editor, Jeni Tennison |
[xsl] template precedence problem, Ben Leighton | Date | [xsl] Regarding XSL performance on , Anand Ganapathy |
Month |