"stoj" <stoj@d...> wrote in message
news:AD9BDA51-058A-4006-8CC4-1369D77C1745@m......
> I need to use a variable (similar scenario also for a template parameter)
> that has been assigned with an xpath string as an xpath expression/match
for
> xsl elements such as xsl:if, xsl:what, xsl:template, etc.
>
> Eg. xsl snippet - intended to invoke execute-code block if the node
exists.
> It works perfectly if i replace "$var" with "/root/parent/child".
>
> <xsl:variable name="var">/root/parent/child</xsl:variable>
> <xsl:if test="$var">
> ...execute-code
> </xsl:if>
>
> 1. Observed behaviour is that the if statement always fires.  Presumably
> because it is resolving to <xsl:if test="'/root/parent/child'">, which
> resolves to true.  If this is true, how can i change this to <xsl:if
> test="/root/parent/child">?  Is there a function availble to strip away
the
> extra quotations?
>
> 2. Does anyone know of a *clean* design pattern to solve this?  Preferably
> one that i can call as a generic template/function to allow it to called
at
> whim.
>
> cheers
> stoj

What you are trying to do is create Dynamic XSL that is XSL that changes as
it's processed.  This is not possible since the XSL is parsed and compiled
in to a processing engine which can not be modified on the fly.

We would need to know more about what you are doing to offer any serious
help.

Some things that might help are xsl:choose, extensive use of templates and
the mode attribute.

Anthony.