The following comment has been added to this issue:

     Author: David Bertoni
    Created: Mon, 20 Sep 2004 9:09 AM
       Body:
Xalan-C gets the same result as OASIS expects, except for the UTF-8 BOM at the 
beginning of the expected file.
---------------------------------------------------------------------
View this comment:
  http://issues.apache.org/jira/browse/XALANJ-1955?page=comments#action_53241

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/XALANJ-1955

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: XALANJ-1955
    Summary: Fail Oasis test case Keys_PerfRepro3
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: XalanJ2
 Components: 
             Xalan-interpretive parser
   Versions:
             2.6

   Assignee: 
   Reporter: elharo

    Created: Mon, 20 Sep 2004 1:12 AM
    Updated: Mon, 20 Sep 2004 9:09 AM

Description:
I'm not 100% sure of this one, but it seems that Xalan fails OASIS tets case 
Keys_PerfRepro3. Possibly the test suite is at fault, but libxslt2 agrees with the 
test suite output, and I can;t see how one could get the reuslts Xalan is getting 
(though keys are tricky, so I and the test suite and libxslt could all be wrong here). 

The problem brgins around line 1189 of the output. Here the expected result is:

</Entity_id><Subsidiaries><Entity_id>034861</Entity_id><Entity_id>034870</Entity_id><Entity_id>03499H</Entity_id><Entity_id>24899Y</Entity_id><Entity_id>604340</Entity_id></Subsidiaries></Entity><Entity><Entity_id>
                        034861
                
</Entity_id><Subsidiaries><Entity_id>025991</Entity_id><Entity_id>03499C</Entity_id><Entity_id>03499G</Entity_id><Entity_id>035128</Entity_id><Entity_id>33799W</Entity_id><Entity_id>899999</Entity_id><Entity_id>94499D</Entity_id></Subsidiaries></Entity><Entity><Entity_id>
                        034919

Xalan's output is similar but not quite the same:

</Entity_id><Subsidiaries><Entity_id>034861</Entity_id><Entity_id>034870</Entity_id><Entity_id>03499H</Entity_id><Entity_id>24899Y</Entity_id><Entity_id>604340</Entity_id><Entity_id>025991</Entity_id><Entity_id>03499C</Entity_id><Entity_id>03499G</Entity_id><Entity_id>035128</Entity_id><Entity_id>33799W</Entity_id><Entity_id>899999</Entity_id><Entity_id>94499D</Entity_id></Subsidiaries></Entity><Entity><Entity_id>
                        034919



---------------------------------------------------------------------
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]

Reply via email to