Project

Profile

Help

Bug #4260

Does deferredValidationMode work?

Added by Michael Kay about 2 months ago. Updated 13 days ago.

Status:
Closed
Priority:
Low
Assignee:
Category:
-
Sprint/Milestone:
-
Start date:
2019-07-24
Due date:
% Done:

100%

Legacy ID:
Applies to branch:
Fix Committed on Branch:
9.9, trunk
Fixed in Maintenance Release:

Description

The schema compiler provides and documents a method to set deferred validation mode (in which validation of the schema is deferred until all schema documents have been loaded). But it appears to be untested. We should either test it, or remove it.

History

#1 Updated by Michael Kay 13 days ago

The reality seems to be somewhere in between "working" and "not working". I've done some experiments, and they basically raise the question, what exactly is this feature supposed to do? It doesn't for example license a schema document to refer to components in another target namespace without having an import for that namespace. Dangling references in a schema are supposed to be allowed anyway, even without this switch.

SchemaCompiler is not a first-class API, so I think we can drop the methods in 10.0 without ceremony, and change 9.9 to make them deprecated.

#2 Updated by Michael Kay 13 days ago

  • Status changed from New to Resolved
  • Fix Committed on Branch 9.9, trunk added

#3 Updated by O'Neil Delpratt 13 days ago

  • Status changed from Resolved to Closed
  • % Done changed from 0 to 100
  • Fixed in Maintenance Release 9.9.1.5 added

Bug fix applied in the Saxon 9.9.1.5 maintenance release.

Please register to edit this issue

Also available in: Atom PDF