The following issue has been updated:
Updater: Brian Minchau (mailto:[EMAIL PROTECTED])
Date: Sat, 4 Sep 2004 4:31 PM
Changes:
assignee changed from Xalan Developers Mailing List
description changed from 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 to 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
environment changed from Operating System: Other
Platform: Other to Operating System: Other
Platform: Other
priority changed to Blocker
Component changed to XSLTC transformation
Component changed from XSLTC
---------------------------------------------------------------------
For a full history of the issue, see:
http://issues.apache.org/jira/browse/XALANJ-1788?page=history
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/XALANJ-1788
Here is an overview of the issue:
---------------------------------------------------------------------
Key: XALANJ-1788
Summary: No error reported for xsl:apply-imports when current template rule is null
Type: Bug
Status: Unassigned
Priority: Blocker
Project: XalanJ2
Components:
XSLTC transformation
Versions:
CurrentCVS
Assignee:
Reporter: Henry Zongaro
Created: Mon, 9 Feb 2004 7:29 PM
Updated: Sat, 4 Sep 2004 4:31 PM
Environment: Operating System: Other
Platform: Other
Description:
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
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.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]
