Subject: RE: [xsl] How to filter element values...|
From: Wendell Piez <wapiez@xxxxxxxxxxxxxxxx>
Date: Sat, 07 Feb 2004 00:17:19 -0500
There is also a built-in template rule for each mode, which allows recursive processing to continue in the same mode in the absence of a successful pattern match by an explicit template rule in the stylesheet. This template rule applies to both element nodes and the root node. The following shows the equivalent of the built-in template rule for mode m.
<xsl:template match="*|/" mode="m"> <xsl:apply-templates mode="m"/> </xsl:template>
It looks like the <xsl:apply-templates mode="g"/> at the bottom of the Global template is causing the default template to get invoked.
Adding a new empty template
<xsl:template match="Global/text() | EVENT/text()" mode="g"/>
Will fixes the problem.
I'm not sure why the default template is being invoked in this case. I read both http://www.w3.org/TR/xslt#modes and http://www.w3.org/TR/xslt#built-in-rule and they seem to be saying that only templates with a matching mode will be invoked. The
Can anyone explain why this is happening?
|<- Previous||Index||Next ->|
|RE: [xsl] How to filter element val, Josh Canfield||Thread||RE: [xsl] How to filter element val, Josh Canfield|
|RE: [xsl] How to filter element val, Josh Canfield||Date||[xsl] Re: text() word lists, Dimitre Novatchev|