DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=27841>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=27841 Current template rule affected by calling named template ------- Additional Comments From [EMAIL PROTECTED] 2004-03-24 19:45 ------- Although XSLT 1.0 is rather vague on this point, the second and third paragraphs of Section 6.7 of latest draft of XSLT 2.0 [2] are pretty explicit about the expected behaviour. They read as follows: << At any point in the processing of a stylesheet, there may be a current template rule. Whenever a template rule is chosen by matching a pattern, the template rule becomes the current template rule for the evaluation of the rule's sequence constructor. When an xsl:for-each or xsl:for-each-group instruction is evaluated, or when a stylesheet function is called (see 10.3 Stylesheet Functions), the current template rule becomes null for the evaluation of that instruction or function. The current template rule is not affected by invoking named templates (see 10.1 Named Templates) or named attribute sets (see 10.2 Named Attribute Sets). While evaluating a global variable or the default value of a stylesheet parameter (see 9.5 Global Variables and Parameters) the current template rule is null. >> I don't believe the XSL WG intended this to be anything other than a clarification of the text that appeared in XSLT 1.0. However, if you'd like me to submit a question about the intended behaviour of XSLT 1.0, I certainly will. [2] http://www.w3.org/TR/xslt20/#apply-imports
