|
Subject: Re: [xsl] workaround for XSLT 1.0 result tree fragment usage? From: "Dimitre Novatchev" <dnovatchev@xxxxxxxxx> Date: Wed, 19 Dec 2007 08:13:13 -0800 |
> MSXML supports an extension function to convert a result tree fragment
> into a node-set, the function is named node-set and is in the namespace
> urn:schemas-microsoft-com:xslt so you can do e.g.
> <xsl:variable name="v1"
> xmlns:msxsl="urn:schemas-microsoft-com:xslt"
> select="msxsl:node-set($confirm_active_program)"/>
> <xsl:when test="not($v1/program[@active =
> 'true'])">
>
Even better, use the
exslt:node-set()
extension function.
It is supported in almost all XSLT 1.0 processors. Microsoft's
XslCompiledTransform supports it, too.
It can be implemented (as Julian Reschke showed) for MSXML as a
Javascript function:
http://www.tkachenko.com/blog/archives/000704.html
--
Cheers,
Dimitre Novatchev
---------------------------------------
Truly great madness cannot be achieved without significant intelligence.
---------------------------------------
To invent, you need a good imagination and a pile of junk
-------------------------------------
Never fight an inanimate object
-------------------------------------
You've achieved success in your field when you don't know whether what
you're doing is work or play
| Current Thread |
|---|
|
| <- Previous | Index | Next -> |
|---|---|---|
| Re: [xsl] workaround for XSLT 1.0 r, Martin Honnen | Thread | Re: [xsl] workaround for XSLT 1.0 r, Don Smith |
| Re: [xsl] workaround for XSLT 1.0 r, Andrew Welch | Date | Re: [xsl] workaround for XSLT 1.0 r, Wendell Piez |
| Month |