Re: [xsl] Error template trumping other templates on import?

[Tony Graham <Tony.Graham@xxxxxxxxxxxxxxxxxxxxxx>]

On Mon, Aug 27 2007 20:21:49 +0100, subsume@xxxxxxxxx wrote:
> I've got master.xsl which is imported by local.xsl. local.xsl also
> includes global.xsl. global.xsl, which contains an error-matching
> template in order to alert me in the case of ambiguous/non-matches. I
> know several of you use a similar template to catch template match
> problems.
>
> My problem is that when included into local.xsl, the error template
> takes over all matches. However, when the templates from master.xsl
> are placed into local.xsl, all is fine. Also, when the error template
> is removed entirely, everything matches as expected.
>
> Is the error matching template causing all templates in master.xsl not
> to be imported?

Import "global.xsl" then import "master.xsl".

Currently, the imported templates in 'master.xsl" have a lower "import
precedence" [1] than the templates in 'local.xsl', and the templates in
'global.xsl' have the higher precedence because they are effectively [2]
part of 'local.xsl'.

Of the templates that you show, the match on "node()" has the same
priority [3] as the match on "*", so when you put the templates in
'master.xsl' into 'local.xsl', it probably only works because the match
on "node()" is effectively later in the stlesheet.

Regards,


Tony Graham.
======================================================================
Tony.Graham@xxxxxxxxxxxxxxxxxxxxxx   http://www.menteithconsulting.com

Menteith Consulting Ltd             Registered in Ireland - No. 428599
Registered Office: 13 Kelly's Bay Beach, Skerries, Co. Dublin, Ireland
----------------------------------------------------------------------
Menteith Consulting -- Understanding how markup works
======================================================================

[1] http://www.w3.org/TR/xslt#import
[2] http://www.w3.org/TR/xslt#include
[3] http://www.w3.org/TR/xslt#conflict