[ http://nagoya.apache.org/jira/browse/XALANJ-1788?page=history ]
Henry Zongaro updated XALANJ-1788:
----------------------------------
Priority: Major (was: Blocker)
> No error reported for xsl:apply-imports when current template rule is null
> --------------------------------------------------------------------------
>
> Key: XALANJ-1788
> URL: http://nagoya.apache.org/jira/browse/XALANJ-1788
> Project: XalanJ2
> Type: Bug
> Components: transformation
> Versions: CurrentCVS
> Environment: Operating System: Other
> Platform: Other
> Reporter: Henry Zongaro
>
> 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
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
