Bug #4994
closed
s9api interface: interaction of SchemaValidator and DocumentBuilder
100%
Description
When a SchemaValidator is set on a DocumentBuilder, the InvalidityReporter set on the SchemaValidator is not actually used to report any validation errors.
Some other less significant properties set on the SchemaValidator also appear to be ignored, for example the options useXsiSchemaLocation, collectStatistics, expandAttributeDefaults, and schema parameters.
Updated by Michael Kay almost 2 years ago
- Status changed from New to In Progress
- Applies to branch 11, trunk added
- Fix Committed on Branch 11, trunk added
- Platforms .NET, Java added
I have
(a) changed DocumentBuilder to pick up additional properties from the SchemaValidator, in particular the options useXsiSchemaLocation, expandAttributeDefaults, and schema parameters.
(b) extended the Javadoc to make it clear how the supplied SchemaValidator is used.
Still to do:
-
More unit tests
-
Equivalent changes for SaxonCS
-
Clarity and test what happens when the document is invalid against the schema: how are the errors reported?
Updated by Michael Kay almost 2 years ago
- Category set to s9api API
- Status changed from In Progress to Resolved
- Priority changed from Low to Normal
I have now arranged for validation parameters and the invalidity handler set on the SchemaValidator to be used, and have added unit tests and API documentation both on SaxonJ and SaxonCS
Updated by Debbie Lockett over 1 year ago
- Status changed from Resolved to Closed
- % Done changed from 0 to 100
- Fixed in Maintenance Release 11.4 added
Bug fix applied in the Saxon 11.4 maintenance release.
Please register to edit this issue
.