Re: [xsl] Daisy chaining XSLT and also how can I check whether the XSLT processor supports a specific extension (specifically, ext:node-set)?

["Martin Honnen martin.honnen@xxxxxx" <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx>]

On 07/08/2024 20:11, ohaya ohaya@xxxxxxxxx wrote:
> I just tried (this was before your response below came in:
>
>
> <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform";
> B B B B B  xmlns:exslt="http://exslt.org/common";
> B B B B B  xmlns:msxsl="urn:schemas-microsoft-com:xslt"
> B B B B B  version="1.0">
> .
> .
> B B B  <xsl:message>Test for exl:node-set() function</xsl:message>
> B B B  <xsl:choose>
> B B B B B B B  <xsl:when test="function-available('exslt:node-set') = ''">
> B B B B B B B B B B B  <xsl:message>+++++++++ exslt:node-set NOT available
> ;)</xsl:message>
> B B B B B B B  </xsl:when>
> B B B B B B B  <xsl:otherwise>
> B B B B B B B B B B B  <xsl:message>+++++++++ exslt:node-set IS
> available</xsl:message>
> B B B B B B B  </xsl:otherwise>
> B B B  </xsl:choose>
>
> And when I test under xsltproc on centos, I get:
>
> Test for exl:node-set() function
> +++++++++ exslt:node-set IS available
>
>
> a) Shouldn't my test (vs. your suggested code) be sufficient?
>
Yes, you can use that to test for support of EXSLT node-set.


> b) Also, per above I ran that on xsltproc on centos...
>
> If the above is good, then I need to try to run the same test on the
> product, but, sorry, I forgot to mention that the product is running
> on Windows, so should I change the namespace prefix in the code to
> "msxsl:" instead of "exslt"?
>

In your previous messages I think you said it is Xalan C++, so no, don't
use the msxsl prefix, it works with Microsoft XSLT 1 processors like the
various versions of MSXML or .NET's obsolete XslTransform.