[EMAIL PROTECTED] wrote:
> > <xsl:template match="sql:query">
> > <xsl:copy>
> > <xsl:apply-templates select="@*|node()"/>
> > </xsl:copy>
> > <xsl:for-each select=".//sql:param">
> > <sql:in-parameter value="[EMAIL PROTECTED]" nr="{position()}"/>
> > </xsl:for-each>
> > </xsl:template>
> >
> > <xsl:template match="sql:param">
> > <xsl:text>?</xsl:text>
> > </xsl:template>
>
> I like it. Add priority="2" to the first match to make certain
> sql:in-parameter elements are created before the sql:param are changed
> to question marks.
From my understanding of XSLT it doesn't change sql:param's to ?s in
the source tree, but only in the result tree, so the processing order
is irrelevant. Actually there is no predefined processing order: XSLT
is (mostly) a declarative programming language free from side effects.
Tobia
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
