DO NOT REPLY [Bug 26801] New: - No error reported for xsl:apply-imports when current template rule is null

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26801>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26801

No error reported for xsl:apply-imports when current template rule is null

           Summary: No error reported for xsl:apply-imports when current
                    template rule is null
           Product: XalanJ2
           Version: CurrentCVS
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: org.apache.xalan.xsltc
        AssignedTo: xalan-dev@xml.apache.org
        ReportedBy: zongaro@ca.ibm.com


According to section 5.6 of XSLT [1], "the current template rule becomes null 
for the instantiation of the content of the xsl:for-each element," and "It is 
an error if xsl:apply-imports is instantiated when the current template rule is 
null."

XSLTC doesn't currently detect this error.  See impinclerr02 for an example.

It should also be detected in an example like the following, which just results 
in a NullPointerException today:

<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
                version="1.0">
  <xsl:variable name="a">
    <xsl:apply-imports/>
  </xsl:variable>
</xsl:stylesheet>

[1] http://www.w3.org/TR/xslt#apply-imports