Issue Details (XML | Word | Printable)

Key: XERCESJ-581
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Assignee: Xerces-J Developers Mailing List
Reporter: Piotr Banski
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Xerces2-J

parser aborts after the external-schemaLocation property is set

Created: 29/Jan/03 11:59 AM   Updated: 13/Apr/04 01:26 AM
Return to search
Component/s: SAX
Affects Version/s: 2.3.0
Fix Version/s: None

Time Tracking:
Not Specified

Environment:
Operating System: Linux
Platform: PC

Bugzilla Id: 16528


 Description  « Hide
This doesn't happen with 2.0.1 or 2.2.1.
When I try to set the property

  "http://apache.org/xml/properties/schema/external-schemaLocation"

the parser aborts with the msgs below, right after I call .parse(uri) on it.

Exception in thread "main" java.lang.ClassCastException:
                                    org.apache.xerces.impl.dv.xs.ListDV$ListData
[Loaded java.lang.StackTraceElement from /usr/java/j2sdk1.4.0_01/jre/lib/rt.jar]
        at
org.apache.xerces.impl.xs.XMLSchemaLoader.processExternalHints(Unknown Source)
        at org.apache.xerces.impl.xs.XMLSchemaValidator.reset(Unknown Source)
        at org.apache.xerces.parsers.BasicParserConfiguration.reset(Unknown Source)
        at org.apache.xerces.parsers.DTDConfiguration.reset(Unknown Source)
        at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)
        at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)
        at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
        at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
        at SAXParser.initParse(SAXParser.java:201)
        at SAXParser.main(SAXParser.java:319)

If I don't try to set the property, everything parses all right (except that I
have to be connected to the Net for the parser to retrieve the schema doc). And
if I set this property for 2.2.1, the schema document is located properly.

Not sure what may matter here, so let me add that I create the parser as:

      parser = XMLReaderFactory.createXMLReader();

and the uri is prepared from the cmdline argument as

      uri = new File(args[i]).toURL().toString();

This looks somewhat related to bug #15878 to my rather ignorant eyes.

 All   Comments   Work Log   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Sandy Gao added a comment - 30/Jan/03 03:28 AM
Fixed in CVS. Some changes in the DV library weren't reflected in other places.

BTW, bug #15878 has nothing to do with this one.

Sandy Gao added a comment - 10/Feb/03 09:56 PM
*** Bug 16902 has been marked as a duplicate of this bug. ***

Sandy Gao added a comment - 22/Feb/03 12:45 AM
*** Bug 17267 has been marked as a duplicate of this bug. ***

Sandy Gao added a comment - 25/Feb/03 10:26 PM
*** Bug 17352 has been marked as a duplicate of this bug. ***

Sandy Gao added a comment - 26/Feb/03 01:46 AM
*** Bug 17382 has been marked as a duplicate of this bug. ***

Neil Graham added a comment - 03/Mar/03 03:50 AM
*** Bug 17550 has been marked as a duplicate of this bug. ***

Neil Graham added a comment - 07/Mar/03 10:30 PM
*** Bug 17732 has been marked as a duplicate of this bug. ***

Neil Graham added a comment - 11/Mar/03 10:10 PM
*** Bug 17861 has been marked as a duplicate of this bug. ***

Neil Graham added a comment - 20/Mar/03 07:51 AM
*** Bug 18172 has been marked as a duplicate of this bug. ***

Neil Graham added a comment - 25/Mar/03 09:54 PM
*** Bug 18310 has been marked as a duplicate of this bug. ***