michael shea

Guys,
I'm having problems using an XML catalog with the Xerces 2 parser. Here is the code that I used to add an entity resolver:
DOMParser parser = new DOMParser(); CatalogResolver catalogResolver = new CatalogResolver(); parser.setEntityResolver(catalogResolver);
I am using version 1.1 of Sun's Resolver package.
The code listed above compiles OK. The following is the CatalogManager.properties file:
CatalogManager.properties # 0 is off, 1 seemed to be also off so far # 2 is reasonable, 4 is very verbosy (including catalog parse success!) verbosity=4 relative-catalogs=yes # Always use semicolons in this list catalogs=/home/acct/mshea/config/catalog.xml prefer=system static-catalog=yes allow-oasis-xml-catalog-pi=yes catalog-class-name=com.sun.resolver.Resolver
When running my program it reads in the catalog correctly, as shown in the following output:
Parse catalog: /home/acct/mshea/config/catalog.xml Loading catalog: /home/acct/mshea/config/catalog.xml Default BASE: file:/home/acct/mshea/config/catalog.xml xml:base: / BASE STR: / system: SchemaFile.xsd file:///home/acct/mshea/generated/schema/SchemaFile.xsd SYSTEM: SchemaFile.xsd file:///home/acct/mshea/generated/schema/SchemaFile.xsd (reset) xml:base: file:/home/acct/mshea/config/catalog.xml BASE STR: file:/home/acct/mshea/config/catalog.xml
This is the catalog.xml files contents:
<?xml version="1.0" encoding="UTF-8"?> <catalog xmlns="urn :-o asis:names:tc:entity:xmlns:xml:catalog" xml:base="/"> <system systemId="SchemaFile.xsd" uri="file:///home/acct/mshea/generated/schema/SchemaFile.xsd"/> </catalog>
The following is the error message that gets return after running the parser:
WARNING: [Warning] null:4:108 schema_reference.4: Failed to read schema document 'SchemaFile.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>. ERROR: [Error] null:4:108 cvc-elt.1: Cannot find the declaration of element 'SchemaFile'. WARNING: [Warning] null:6:20 schema_reference.4: Failed to read schema document 'SchemaFile.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>. ERROR: [Error] null:6:20 cvc-elt.1: Cannot find the declaration of element 'name'. WARNING: [Warning] null:7:16 schema_reference.4: Failed to read schema document 'SchemaFile.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>. ERROR: [Error] null:7:16 cvc-elt.1: Cannot find the declaration of element 'description'. WARNING: [Warning] null:9:11 schema_reference.4: Failed to read schema document 'SchemaFile.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>. ERROR: [Error] null:9:11 cvc-elt.1: Cannot find the declaration of element 'line'. WARNING: [Warning] null:11:10 schema_reference.4: Failed to read schema document 'SchemaFile.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>. ERROR: [Error] null:11:10 cvc-elt.1: Cannot find the declaration of element 'label'.
Each time the error occurs, the entity resolver tries to resolve the following:
resolveSystem(file:///home/acct/mshea/config/SchemaFile.xsd)
I don't know why it adds the base directories to the name of the schema file as I have explicitly told the entity resolver to not use absolute locations.
Lastly, here is a sample of the xml file which contains the "lookup name" for the xml catalog to look up:
<?xml version="1.0" encoding="UTF-8"?> <SchemaFile xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.doesnotexist.com/SchemaFile" xsi:schemaLocation="http://www.doesnotexist.com/SchemaFile SchemaFile.xsd"> <name>test</name> <description>test desc </description> <label>test label</label> </SchemaFile>
As you can see, the xml file only references SchemaFile.xsd, and the entity resolver at runtime should lookup that name in the catalog and substitute file:///home/acct/mshea/generated/schema/SchemaFile.xsd for it, but it does not.
Any help would be appreciated and if I'm doing this the wrong way, then I'd definately want to nkow about it.
Thanks.

Senthil, I'm not sure what code you wanted, but here is the code that I use and it dynamically validates xml files with the 1.4.4 parser.
try { InputSource inputSource = new InputSource(getReader()); DOMParser parser = new DOMParser(); parser.setErrorHandler(this); parser.setFeature("http://apache.org/xml/features/validation/schema", true); parser.setFeature("http://apache.org/xml/features/validation/dynamic", true); parser.setFeature("http://xml.org/sax/features/namespaces", true); parser.parse(inputSource); Document doc = parser.getDocument(); } catch (SAXNotRecognizedException ex) { } catch (SAXNotSupportedException ex) { } catch (SAXException ex) { } catch (IOException ex) { }

Guys, just to let you know and anyone else who has run into the same problem. I updated the Xerces parser to the latest (1.4.4) and the dynamic feature works correctly as it should.
Thanks for all the help.

Does anyone know when Xerces 2 will be released? It must getting close now if its up to beta 3.
Thanks.

Yep, I've set the errorHandler and it still has the same problem. I beginning to think that the Dynamic feature is not yet implemented. I may have to email the Xerces-J-User mailing list to see if anyone knows more about this.
[This message has been edited by michael shea (edited November 13, 2001).]

Originally posted by arul senthil:

Doesn't these two options appear complementary?

Yes, good point but I've also tried that and it still doesn't work. I've also tried using the sample DOMCount.java that came in the Xerces package. It too has the same problem. Could it be because the schema is incorrectly declared in the xml file? Here is a sample:
<MetaCBEntityChild xmlns="http://www.company.com/MetaCBEntity" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.company.com/MetaCBEntity file:///sc/mshea/src/conftool/schema/MetaCBEntity.xsd"> ... ... ... </MetaCBEntityChild>

Actually the more i think about it, i realise that this may be a bug!?!? in the software. Could this be the case?

Thanks for the reply. I actually may have the said the wrong version because we can validate against a schema. It works fine without the setFeature(dynamic, true) line in the code, except it validates all files, including those without schema's specified, which results in a whole bunch of errors being displayed)

Guys, as the subject suggests, i have turned on validation via:
parser.setFeature("http://xml.org/sax/features/validation", true); parser.setFeature("http://apache.org/xml/features/validation/schema-full-checking", true); parser.setFeature("http://apache.org/xml/features/validation/dynamic", true);
The reason I've set dynamic to true is because if an xml file does not include a schema to validate against, then I do NOT want to validate the xml file, however, if a schema has been specified, then i want to validate the xml file. The problem is that the xml files are never validated regardless of whether or not an xml file has specified a schema. (I've also sabotaged a few xml files to deliberately introduce known errors into the xml so i can see if it has been validated).
Thanks for any information.
Edit:
I forgot to say which parser: Its Xerces 1.4 using the DOM Parser.
[This message has been edited by michael shea (edited November 11, 2001).]