Project

Profile

Help

Bug #6255

closed

Configuration file option global/@parser="#DEFAULT" invalid against schema

Added by Debbie Lockett 6 months ago. Updated 5 months ago.

Status:
Resolved
Priority:
Normal
Category:
Configuration
Sprint/Milestone:
-
Start date:
2023-11-16
Due date:
% Done:

0%

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

Description

In the fix for Bug #6015: Using the default JDK parser, the option "#DEFAULT" was added for FeatureKeys.SOURCE_PARSER_CLASS as a way of requesting the default internal parser. But the configuration file schema has not been updated to allow this. The schema says the "parser" attribute has type="c:javaClassNameType".

(The fix should be made in src/samples/config/config-raw.xsd, which is used to generate the schema supplied in the Saxon resources.)

Actions #1

Updated by Debbie Lockett 6 months ago

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

Fix in src/samples/config/config-raw.xsd to add new type for global/@parser which accepts c:javaClassNameType or the string "#DEFAULT".

Fix committed on main, saxon12, and saxon11 branches.

Actions #2

Updated by O'Neil Delpratt 5 months ago

  • Fixed in Maintenance Release 12.4 added

Bug fix applied in the Saxon 12.4 Maintenance release. Leaving it marked as 'Resolved' until fix applied on Saxon 11.

Please register to edit this issue

Also available in: Atom PDF