Bug #2666
closed
JAXP Validator.validate() throws an exception if there are validation errors
Applies to branch:
9.6, 9.7
Fix Committed on Branch:
9.6, 9.7
Fixed in Maintenance Release:
Description
Saxon's implementation of the JAXP Validate class (com.saxonica.ee.jaxp.ValidatorImpl) throws an exception from the validate() method (saying "One or more validation errors were reported") if any validity problems were found.
Demonstrated by unit test TestValidator.testSchemaListener().
The spec isn't 100% unambiguous on this, but it seems that no exception is expected.
I've back-ported the relevant unit test to 9.6 and it fails in the same way there. So this isn't a 9.7 regression.
I have added a Xerces version of the unit test which demonstrates that the Xerces implementation of the JAXP SchemaFactory does not throw an exception from the validate() method.
- Category set to JAXP Java API
- Assignee set to Michael Kay
- Applies to branch 9.6 added
- Fix Committed on Branch 9.6, 9.7 added
Patch committed on both the 9.6 and 9.7 branches.
Note: in the case of 9.6, I also fixed a separate bug: errors in unique/key/keyref constraints were being notified to ErrorHandler.fatalError() rather than ErrorHandler.error().
- Status changed from New to Resolved
- % Done changed from 0 to 100
- Fixed in Maintenance Release 9.7.0.4 added
Bug fix applied in the Saxon 9.7.0.4 maintenance release. Leave open until patched applied in the 9.6 maintenance release.
- Status changed from Resolved to Closed
- Fixed in Maintenance Release 9.6.0.9 added
- Fixed in Maintenance Release deleted (
9.7.0.4)
Bug fix applied in the Saxon 9.6.0.9 maintenance release.
- Sprint/Milestone set to 9.7.0.4
- Fixed in Maintenance Release 9.7.0.4 added
Please register to edit this issue
Also available in: Atom
PDF
.