This is the mail archive of the xsl-list@mulberrytech.com mailing list .


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

RE: conflicting template rules


> [...]
> 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.

It is covered by the standard: 
"It is an error if this leaves more than one matching template rule [ie if
more than one matching template rule have exactly the same priority]. An
XSLT processor may signal the error; if it does not signal the error, it
must recover by choosing, from amongst the matching template rules that are
left, the one that occurs last in the stylesheet."

Section 5.5 of the XSLT spec, at http://www.w3.org/TR/xslt#conflict

Linda 


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

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]