Bug 8053 - SAXParser leaves XSD files locked on error
Summary: SAXParser leaves XSD files locked on error
Status: NEW
Alias: None
Product: Xerces-J
Classification: Unclassified
Component: SAX (show other bugs)
Version: 1.4.3
Hardware: PC All
: P3 normal
Target Milestone: ---
Assignee: Xerces-J Developers Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-04-13 20:02 UTC by Mark Woodruff
Modified: 2005-03-20 17:06 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mark Woodruff 2002-04-13 20:02:43 UTC
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).