Support #5979
closed
Java 11 || Saxon9.9 EE || XmlCatalogResolver.setCatalog(catalogFile, processor.getUnderlyingConfiguration(), true) not working as expected like cmd line validation
0%
Description
Hi,
We are working on the setup of validating the xml, dita, ditamap using saxon EE
XmlCatalogResolver.setCatalog(catalogFile, processor.getUnderlyingConfiguration(), true);
the above line is used to resolve the catalog files, but it's able to resolve URI partially because of that validation throws error "One validation error was reported: Cannot validate <Q{}topic>: no element declaration available" "Validation will continue without the schema at urn:test.dita.v1_3.com:dita:xsd:topic.xsd"
topic.xsd file is present in catalog file but this is not getting resolved.
Note: xml resolver 1.2 is added in our POM file
Please help us to get moving from this issue.
Updated by Norm Tovey-Walsh over 1 year ago
We are working on the setup of validating the xml, dita, ditamap using saxon EE
XmlCatalogResolver.setCatalog(catalogFile, processor.getUnderlyingConfiguration(), true);
the above line is used to resolve the catalog files, but it's able to resolve URI partially
because of that validation throws error "One validation error was reported: Cannot validate <Q
{}topic>: no element declaration available" "Validation will continue without the schema at
urn:test.dita.v1_3.com:dita:xsd:topic.xsd"topic.xsd file is present in catalog file but this is not getting
resolved.
Can you provide a test case that demonstrates the problem? Saxon 9.9
uses the Apache resolver so I think 1.2 is the right version, but a test
case would help.
Be seeing you,
norm
--
Norm Tovey-Walsh
Saxonica
Updated by Norm Tovey-Walsh 10 months ago
- Status changed from New to Closed
No additional details provided. Please reopen if you can provide a test case.
Please register to edit this issue
.