This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
conflicting template rules
- To: "'XSL-List at mulberrytech dot com'" <XSL-List at mulberrytech dot com>
- Subject: conflicting template rules
- From: Schlee Stefan <ssch at ticon dot at>
- Date: Fri, 1 Dec 2000 13:28:32 +0100
- Reply-To: xsl-list at mulberrytech dot com
The standard states rules for resolution of conflicts between template rules
to which different priorities can be assigned or
template rules which are imported (included) from different sources into the
same XSLT file. What I miss are rules for resovling
the conflict that arises if two or more template rules are specified in the
same XSLT with exactly the same priority, for example:
<?xml version='1.0'?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
version="1.0">
<xsl:template match="USERLIST">
<test1>XXX</test1>
</xsl:template>
<xsl:template match="USERLIST">
<test2>YYY</test2>
</xsl:template>
</xsl:stylesheet>
xalan only outputs the "test2" element. Is this behaviour covered by the
standard or is it parser specific.
Thank you for your help
Stefan Schlee / TICon
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list