DO NOT REPLY [Bug 8053] New: - SAXParser leaves XSD files locked on error

[bu...@apache.org]

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=8053>.
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=8053

SAXParser leaves XSD files locked on error

           Summary: SAXParser leaves XSD files locked on error
           Product: Xerces-J
           Version: 1.4.3
          Platform: PC
        OS/Version: Windows 9x
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: SAX
        AssignedTo: xerces-j-dev@xml.apache.org
        ReportedBy: nothimtheotherguy@yahoo.com


If a program using org.apache.xerces.parsers.SAXParser attempts to parse a local
XML file that uses a local XSD schema and the schema has an error, the parser
reports the error but leaves the schema file opened and locked, which prevents
someone from editing the file to fix the problem. For example:

<?xml version="1.0" encoding="UTF-8"?>
<db xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:noNamespaceSchemaLocation="db.xsd">
</db>

If db.xsd has a syntax error, the parser will report it correctly but leave
db.xsd opened and locked (rather than closing it as it should). Not a good thing
when the parser in question is being invoked inside an web server (e.g. TomCat).

---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org