[ http://issues.apache.org/jira/browse/XALANJ-1938?page=all ]
Brian Minchau updated XALANJ-1938:
----------------------------------
Fix Version: 2.7.0-future-release
Description:
key() and id() give wrong results with XSLTC.
Testcase (to be attached):
XSLTC (java org.apache.xalan.xslt.Process -XSLTC -IN test.xml -XSL test.xsl
-PARAM access none -PARAM user one) outputs "none" which is incorrect.
Xalan (java org.apache.xalan.xslt.Process -IN test.xml -XSL test.xsl -PARAM
access none -PARAM user one) outputs "one" which is correct.
The bug seems to be related to using one xsl:key from various key() functions.
The real-world transformation this testcase was derived from fails in the same
way if id() is used instead of key().
Priority for this bug is set to critical: With this bug transformations leak
information as there is no indication of malfunctioning, and not only is
information dropped but information is shown that is not intended to be shown.
was:
key() and id() give wrong results with XSLTC.
Testcase (to be attached):
XSLTC (java org.apache.xalan.xslt.Process -XSLTC -IN test.xml -XSL test.xsl
-PARAM access none -PARAM user one) outputs "none" which is incorrect.
Xalan (java org.apache.xalan.xslt.Process -IN test.xml -XSL test.xsl -PARAM
access none -PARAM user one) outputs "one" which is correct.
The bug seems to be related to using one xsl:key from various key() functions.
The real-world transformation this testcase was derived from fails in the same
way if id() is used instead of key().
Priority for this bug is set to critical: With this bug transformations leak
information as there is no indication of malfunctioning, and not only is
information dropped but information is shown that is not intended to be shown.
Marking for 2.7 release, per JIRA meeting on June 7, 2005.
> key() and id() results are incorrect, works with Xalan
> ------------------------------------------------------
>
> Key: XALANJ-1938
> URL: http://issues.apache.org/jira/browse/XALANJ-1938
> Project: XalanJ2
> Type: Bug
> Components: XSLTC
> Versions: 2.6
> Environment: Linux, Sun-JRE 1.3.1_03
> Reporter: Stephan Feder
> Assignee: Henry Zongaro
> Priority: Critical
> Fix For: 2.7.0-future-release
> Attachments: j1938.patch2.txt, patch.j1938.txt, test.xml, test.xsl
>
> key() and id() give wrong results with XSLTC.
> Testcase (to be attached):
> XSLTC (java org.apache.xalan.xslt.Process -XSLTC -IN test.xml -XSL test.xsl
> -PARAM access none -PARAM user one) outputs "none" which is incorrect.
> Xalan (java org.apache.xalan.xslt.Process -IN test.xml -XSL test.xsl -PARAM
> access none -PARAM user one) outputs "one" which is correct.
> The bug seems to be related to using one xsl:key from various key() functions.
> The real-world transformation this testcase was derived from fails in the
> same way if id() is used instead of key().
> Priority for this bug is set to critical: With this bug transformations leak
> information as there is no indication of malfunctioning, and not only is
> information dropped but information is shown that is not intended to be shown.
--
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
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
