Extension elements and fallbacks...

[Norman Walsh <nd...@nwalsh.com>]

I'm using the following code to implement "chunked output" in a
variety of XSLT processors:

  <xt:document method="html" href="{$chunkfn}">
    <xsl:call-template name="chunk-element-content">
      <xsl:with-param name="prev" select="$prev"/>
      <xsl:with-param name="next" select="$next"/>
    </xsl:call-template>
    <xsl:fallback>
      <xalanredirect:write file="{$chunkfn}">
	<xsl:call-template name="chunk-element-content">
	  <xsl:with-param name="prev" select="$prev"/>
	  <xsl:with-param name="next" select="$next"/>
	</xsl:call-template>
	<xsl:fallback>
	  <saxon:output method="html" file="{$chunkfn}">
	    <xsl:call-template name="chunk-element-content">
	      <xsl:with-param name="prev" select="$prev"/>
	      <xsl:with-param name="next" select="$next"/>
	    </xsl:call-template>
	    <xsl:fallback>
	      <xsl:call-template name="chunk-element-content">
		<xsl:with-param name="prev" select="$prev"/>
		<xsl:with-param name="next" select="$next"/>
	      </xsl:call-template>
	    </xsl:fallback>
	  </saxon:output>
	</xsl:fallback>
      </xalanredirect:write>
    </xsl:fallback>
  </xt:document>

(With appropriate xmlns: and extension-element-prefixes, naturally)

But (recent?) releases of Xalan seem to make a vain attempt to get
Java code back from the xt namespace URI when I would expect them to
perform the xsl:fallback action.

Comments?

                                        Be seeing you,
                                          norm

-- 
Norman.Walsh@East.Sun.COM | It is good to have an end to journey
XML Technology Center     | toward; but it is the journey that matters,
Sun Microsystems, Inc.    | in the end.--Ursula K. Le Guin