This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Re: xsl:fallback, nodesets, and different processors
- To: <xsl-list at lists dot mulberrytech dot com>
- Subject: Re: [xsl] xsl:fallback, nodesets, and different processors
- From: "Aleksei Valikov" <valikov at fzi dot de>
- Date: Thu, 16 Aug 2001 09:09:47 +0200
- References: <00a301c125ee$83f8f660$ca2110ac@niku.com>
- Reply-To: xsl-list at lists dot mulberrytech dot com
Hi.
> I want to make the XSLT 1.0 version [i.e.,
> "$cellFilter/table/cell" instead of
> "xalan:nodeset($cellFilter)/table/cell"] the norm and
> the Xalan extension the exception. I tried, but the
> fallback doesn't work within the for-each tag.
XPath 1.0 does not allow anything to be converted to a node-set. Probably
you meant an older version.
Probably something like
<span xsl:version="1.1">
<xsl:for-each select="$cellFilter/....">
<!-- do something if 1.1 version is supported -->
</xsl:for-each>
<xsl:fallback>
<!-- if version 1.1. is not supported -->
<xsl:for-each select="xalan:nodeset($cellFilter)/....">
<!-- do something -->
</xsl:for-each>
</xsl:fallback>
</span>
>
> Should I even be trying to use the <xsl:fallback>
> element here, or is there some other way to accomplish
> what I want to do? I would appreciate any suggestions
> or strategies.
Time could be one. We'll have no nodeset problems with 2.0.
Bye.
/lexi
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list