You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xalan.apache.org by bu...@apache.org on 2001/11/29 00:24:44 UTC

DO NOT REPLY [Bug 5172] New: - Xerces144: SAXResultAPITest holds result files open, ambg result

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5172>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5172

Xerces144: SAXResultAPITest holds result files open, ambg result

           Summary: Xerces144: SAXResultAPITest holds result files open,
                    ambg result
           Product: XalanJ2
           Version: CurrentCVS
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: org.apache.xalan.serialize
        AssignedTo: xalan-dev@xml.apache.org
        ReportedBy: curcuru@apache.org


After switching to xerces.jar from 1.4.4, the smoketest fails with the 
SAXResultAPITest having several AMBG results because the fileChecker call can't 
open the actual output file (Even though I've explicitly .close()d the 
FileOutputStream that underlies the SAXResult being used).  Worked fine with 
Xerces 1.4.3
TestID: SAXResultAPITest r1.5 testCase3
Note that the identityTransformer portion of the test seems to work fine and 
passes, it's when you use a 'real' transformer that it locks the file. Note 
that the file contents are correct if you view them after the test completes. 
Note also that the logging ContentHandler and LexicalHandler that are plugged 
into the SAXResult do appear to be getting (and logging) all the correct events.