Project

Profile

Help

Bug #4677

closed

JUnit Tests testMultipleSchemaImportsOn and testMultipleSchemaImportsOff in TestValidator

Added by Michael Kay over 3 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Schema-Aware processing
Sprint/Milestone:
-
Start date:
2020-08-11
Due date:
% Done:

100%

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

Description

These unit tests are currently failing in both 9.9 and 10.1. I'm not aware of any change that might have caused this but it could be a regression caused by a patch for some other bug.

The problem appears to be that a URIResolver set on the Configuration is not being used to resolve xs:import schemaLocation attributes.

Actions #1

Updated by Michael Kay over 3 years ago

The test passes in 9.8. In 9.8, the StandardSchemaResolver falls back to getting the Configuration's URIResolver during execution of the resolve() method. In 9.9 and 9.10, the StandardSchemaResolver gets the Configuration's URIResolver at the time the StandardSchemaResolver is instantiated, which is too early.

Actions #2

Updated by Michael Kay over 3 years ago

The change was made while fixing bug #4323.

Actions #3

Updated by Michael Kay over 3 years ago

  • Status changed from New to Resolved
  • Applies to branch 10, 9.9, trunk added
  • Fix Committed on Branch 10, 9.9, trunk added
Actions #4

Updated by O'Neil Delpratt over 3 years ago

  • % Done changed from 0 to 100
  • Fixed in Maintenance Release 10.2 added

Bug fix applied in the Saxon 10.2 maintenance release.

Actions #5

Updated by O'Neil Delpratt over 3 years ago

  • Status changed from Resolved to Closed
  • Fixed in Maintenance Release 9.9.1.8 added

Bug fix applied on the Saxon 9.9.1.8 maintenance release.

Please register to edit this issue

Also available in: Atom PDF