Subject: RE: [xsl] xsl:apply-imports vs xsl:next-match From: "mike@xxxxxxxxxxxx" <mike@xxxxxxxxxxxx> Date: Fri, 31 Mar 2006 09:28:40 -0500 |
I would always use xsl:next-match in preference. Treat apply-imports as being retained for backwards compatibility. Part of the logic when apply-imports was designed was that the person who writes the stylesheet module containing the apply-imports call should be able to predict which template is going to be called next, because it will always be in the subtree imported by that module. xsl:next-match doesn't have this feature. But I would still use xsl:next-match in preference. Michael Kay http://www.saxonica.com/ Original Message: ----------------- From: tom tom tomxsllist@xxxxxxxxxxx Date: Fri, 31 Mar 2006 14:27:19 +0100 To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx Subject: [xsl] xsl:apply-imports vs xsl:next-match Hi I need to decide on rules for when to use the xsl:apply-imports element and when to use xsl:next-match. I understand that xsl:next-match can be invoked by multiple template rules in the same file, xsl:apply-imports cannot. I can not quite figure out a situation in which xsl:apply-imports has an advantage over xsl:next-match if the priorities for xsl:next-match have been set up in an appropriate manner. If this is true am I losing anything by omitting the use of xsl:apply-imports altogether? Thanks Tom _________________________________________________________________ Be the first to hear what's new at MSN - sign up to our free newsletters! http://www.msn.co.uk/newsletters -------------------------------------------------------------------- mail2web - Check your email from the web at http://mail2web.com/ .
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] xsl:apply-imports vs xsl:, David Carlisle | Thread | [xsl] [ANNOUNCE] Invoking Web Servi, Stylus Studio |
Re: [xsl] xsl:apply-imports vs xsl:, David Carlisle | Date | [xsl] [ANNOUNCE] Invoking Web Servi, Stylus Studio |
Month |