This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
namespaces and extensions and multiple files
- To: xsl-list at mulberrytech dot com
- Subject: namespaces and extensions and multiple files
- From: Sebastian Rahtz <sebastian dot rahtz at computing-services dot oxford dot ac dot uk>
- Date: Thu, 27 Jul 2000 10:06:33 +0100 (BST)
- References: <69A1202FA707D411AA3E00508BCF7E54C8DAA7@cedelbank.com>
- Reply-To: xsl-list at mulberrytech dot com
I want my XSL file to handle all the variants of the "multiple output
file" scenario; to avoid a load of namespace declarations at the
front, I thought I'd be clever and use the "xmlns" attribute on the
extension element itself, thusly:
<xsl:when test="contains($processor,'Clark')">
<document xmlns="http://www.jclark.com/xt" href="{$filename}">
<xsl:call-template name="writestone"/>
</document>
</xsl:when>
<xsl:when test="contains($processor,'SAXON')">
<output xmlns="http://icl.com/saxon" file="{$filename}">
<xsl:call-template name="writestone"/>
</output>
</xsl:when>
<xsl:when test="contains($processor,'Apache')">
<write xmlns="org.apache.xalan.xslt.extensions.Redirect" file="{$filename}">
<xsl:call-template name="writestone"/>
</write>
</xsl:when>
<xsl:when test="contains($processor,'Oracle')">
<output use="oout" xmlns="http://www.oracle.com/XSL/Transform/java" href="{$filename}">
<xsl:call-template name="writestone"/>
</output>
XT accepts this, and does what I expect. The other three don't. Would
anyone care to express a view on whether this *should* work?
Sebastian Rahtz
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list