Project

Profile

Help

Feature #3141

closed

fn:parse-xml should respect configuration's parse options

Added by Gunther Rademacher about 7 years ago. Updated almost 7 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Internals
Sprint/Milestone:
-
Start date:
2017-02-23
Due date:
% Done:

100%

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

Description

My attempts to use

configuration.getParseOptions().addParserFeature("http://apache.org/xml/features/nonvalidating/load-external-dtd", false);
for configuring the parser used by fn:parse-xml were not successful. A look at the source code showed that ParseXml.evalParseXml has
ParseOptions options = new ParseOptions();
ParseOptions options = configuration.getParseOptions();
Actions #1

Updated by Michael Kay about 7 years ago

  • Category set to Internals
  • Status changed from New to Resolved
  • Assignee set to Michael Kay
  • Priority changed from Low to Normal
  • Applies to branch 9.8 added
  • Fix Committed on Branch 9.7, 9.8 added

Agreed.

Though the correct code is

ParseOptions options = new ParseOptions(configuration.getParseOptions());

because the code given would cause the default ParseOptions in the Configuration to be modified.

I have made the change on the 9.7 and 9.8 branches, and regression tested.

Actions #2

Updated by O'Neil Delpratt about 7 years ago

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

Bug fix applied in the Saxon 9.7.0.18 maintenance release.

Actions #3

Updated by O'Neil Delpratt almost 7 years ago

  • Fix Committed on Branch trunk added
  • Fix Committed on Branch deleted (9.8)
Actions #4

Updated by O'Neil Delpratt almost 7 years ago

  • Applies to branch deleted (9.8)

Please register to edit this issue

Also available in: Atom PDF