You are viewing a plain text version of this content. The canonical link for it is here.
Posted to j-dev@xerces.apache.org by xe...@xml.apache.org on 2004/09/07 20:11:37 UTC

[jira] Created: (XERCESJ-1008) key() and id() results are incorrect, works with Xalan

Message:

  A new issue has been created in JIRA.

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/XERCESJ-1008

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: XERCESJ-1008
    Summary: key() and id() results are incorrect, works with Xalan
       Type: Bug

     Status: Unassigned
   Priority: Critical

    Project: Xerces2-J
   Versions:
             2.6.0

   Assignee: 
   Reporter: Stephan Feder

    Created: Tue, 7 Sep 2004 11:10 AM
    Updated: Tue, 7 Sep 2004 11:10 AM
Environment: Linux, Sun-JRE 1.3.1_03

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.



---------------------------------------------------------------------
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: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org

[jira] Updated: (XERCESJ-1008) key() and id() results are incorrect, works with Xalan

Posted by xe...@xml.apache.org.
The following issue has been updated:

    Updater: Stephan Feder (mailto:sf@b-i-t.de)
       Date: Tue, 7 Sep 2004 11:11 AM
    Comment:
The test data: test.xml
    Changes:
             Attachment changed to test.xml
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://issues.apache.org/jira/browse/XERCESJ-1008?page=history

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/XERCESJ-1008

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: XERCESJ-1008
    Summary: key() and id() results are incorrect, works with Xalan
       Type: Bug

     Status: Unassigned
   Priority: Critical

    Project: Xerces2-J
   Versions:
             2.6.0

   Assignee: 
   Reporter: Stephan Feder

    Created: Tue, 7 Sep 2004 11:10 AM
    Updated: Tue, 7 Sep 2004 11:11 AM
Environment: Linux, Sun-JRE 1.3.1_03

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.



---------------------------------------------------------------------
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: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org

[jira] Updated: (XERCESJ-1008) key() and id() results are incorrect, works with Xalan

Posted by xe...@xml.apache.org.
The following issue has been updated:

    Updater: Stephan Feder (mailto:sf@b-i-t.de)
       Date: Tue, 7 Sep 2004 11:12 AM
    Comment:
The test stylesheet: test.xsl
    Changes:
             Attachment changed to test.xsl
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://issues.apache.org/jira/browse/XERCESJ-1008?page=history

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/XERCESJ-1008

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: XERCESJ-1008
    Summary: key() and id() results are incorrect, works with Xalan
       Type: Bug

     Status: Unassigned
   Priority: Critical

    Project: Xerces2-J
   Versions:
             2.6.0

   Assignee: 
   Reporter: Stephan Feder

    Created: Tue, 7 Sep 2004 11:10 AM
    Updated: Tue, 7 Sep 2004 11:12 AM
Environment: Linux, Sun-JRE 1.3.1_03

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.



---------------------------------------------------------------------
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: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org