Project

Profile

Help

Bug #2666

closed

JAXP Validator.validate() throws an exception if there are validation errors

Added by Michael Kay about 8 years ago. Updated almost 8 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
JAXP Java API
Sprint/Milestone:
Start date:
2016-03-08
Due date:
% Done:

100%

Estimated time:
Legacy ID:
Applies to branch:
9.6, 9.7
Fix Committed on Branch:
9.6, 9.7
Fixed in Maintenance Release:
Platforms:

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.

Actions #1

Updated by Michael Kay about 8 years ago

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.

Actions #2

Updated by Michael Kay about 8 years ago

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.

Actions #3

Updated by Michael Kay about 8 years ago

  • 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().

Actions #4

Updated by Michael Kay about 8 years ago

  • Status changed from New to Resolved
Actions #5

Updated by O'Neil Delpratt about 8 years ago

  • % 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.

Actions #6

Updated by O'Neil Delpratt almost 8 years ago

  • 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.

Actions #7

Updated by O'Neil Delpratt almost 8 years ago

  • 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