RE: [xsl] fallback, saxon and MSXSL

["Michael Kay" <michael.h.kay@xxxxxxxxxxxx>]

<xsl:fallback> is activated when it's inside an instruction that the
processor doesn't recognize, it's not activated for missing extension
functions.

Use <xsl:if test="function-available('msxsl:node-set')">

or test the result of system-property('xsl:vendor')

Michael Kay
Software AG
home: Michael.H.Kay@xxxxxxxxxxxx
work: Michael.Kay@xxxxxxxxxxxxxx 
      

> -----Original Message-----
> From: owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx 
> [mailto:owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of 
> DPawson@xxxxxxxxxxx
> Sent: 09 October 2002 10:51
> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> Subject: [xsl] fallback, saxon and MSXSL
> 
> 
> Trying to get a template to work with both processors (don't ask).
> 
> 
> The instruction is a for-each.
> 
> 
> I have
> 
>  <extn>
>       <xsl:for-each 
> select="msxsl:node-set($test)/extns/ext[not(.=preceding-siblin
> g::ext)]">
>         <xsl:fallback>
>           <xsl:for-each 
> select="$test/extns/ext[not(.=preceding-sibling::ext)]"> 
>              <ext><xsl:value-of select="."/></ext>
>         </xsl:for-each>
>       </xsl:fallback>
>       <ext><xsl:value-of select="."/></ext>
>     </xsl:for-each>
>   </extn>
> 
> The structure seems right for fallback,
> but if I put MS first, with saxon as the fallback,
>  Mike complains:
>   The URI urn:schemas-microsoft-com:xslt does not identify an 
> external Java class
> 
> which is kinda fair comment.... 
>   but doesn't help me here. Is it compliant Mike?
>   (Noted that it mostly is, and I guess I could put the saxon 
> call first.) Do I have to use function-available instead?
> 
> Regards DaveP.
> 
> **** snip here *****
> 
> - 
> 
> NOTICE: The information contained in this email and any 
> attachments is 
> confidential and may be legally privileged. If you are not the 
> intended recipient you are hereby notified that you must not use, 
> disclose, distribute, copy, print or rely on this email's content. If 
> you are not the intended recipient, please notify the sender 
> immediately and then delete the email and any attachments from your 
> system.
> 
> RNIB has made strenuous efforts to ensure that emails and any 
> attachments generated by its staff are free from viruses. However, it 
> cannot accept any responsibility for any viruses which are 
> transmitted. We therefore recommend you scan all attachments.
> 
> Please note that the statements and views expressed in this email 
> and any attachments are those of the author and do not necessarily 
> represent those of RNIB.
> 
> RNIB Registered Charity Number: 226227
> 
> Website: http://www.rnib.org.uk 
> 
>  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
> 


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list