[XERCESJ-1211] Use of DOMInputSource causes null entries in XSNamespaceItem.getDocumentLocations().

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.8.1, 2.9.0, 2.9.1
• Fix Version/s: 2.10.0
• Component/s: XML Schema API
• Environment: Linux.
• Assignee: Michael Glavassevich
• Reporter: Chris Simmons
• Created: 09/Nov/06 17:41
• Updated: 22/Nov/09 18:39
• Resolved: 07/Jan/09 07:04

Description

I've written a test which I will shortly attach where I load a schema grammar using DOMInputSource. The resulting schema grammar's document locations list contains a null entry.

I think this is due to the different code path followed when using dom inputs. The normal path loads the schema from a stream and hits the following code in XSDHandler.getSchemaDocument():-

// now we need to store the mapping information from system id
// to the document. also from the document to the system id.
if (key != null)
fTraversed.put(key, schemaElement );
if (schemaId != null)
fDoc2SystemId.put(schemaElement, schemaId );
fLastSchemaWasDuplicate = false;
return schemaElement;

The document isn't being put in fDoc2SystemId when using DOMInputSource. Perhaps it would be more robust if XSDHandler was responsible for dealing with dom inputs, and just directly used the dom when it normally parses the XML?

I need the document locations field in order to figure out which documents a schema grammar depends upon, in case some are modified or reloaded.