Project

Profile

Help

Bug #5756

closed

SaplingElement has incorrect NamespaceMap, resulting in spurious `xmlns=""`

Added by Michael Kay about 1 year ago. Updated about 1 year ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Internals
Sprint/Milestone:
-
Start date:
2022-12-06
Due date:
% Done:

100%

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

Description

When a SaplingElement is created, with a no-namespace element name, it is given a NamespaceMap containing the namespace binding xmlns="". As the documentation for class NamespaceMap makes clear, the map should never contain any namespace undeclarations.

The consequence is that when the SaplingElement is serialised, a spurious xmlns="" may appear in the serialised output.

The SaplingElement is used in the implementation of the sql:query extension instruction, and the bug manifests itself as incorrect output for test case sql-005.

Actions #1

Updated by Michael Kay about 1 year ago

  • Category set to Internals
  • Status changed from New to Resolved
  • Priority changed from Low to Normal
  • Applies to branch 10, 11, trunk added
  • Fix Committed on Branch 10, 11, trunk added
  • Platforms .NET, Java added
Actions #2

Updated by Community Admin about 1 year ago

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

Bug issue fix applied in the Saxon 12.0 Major Release. Leaving this bug marked as Resolved until fix applied

Actions #3

Updated by O'Neil Delpratt about 1 year ago

  • Fixed in Maintenance Release 11.5 added

Bug fix applied in the Saxon 11.5 maintenance release.

Actions #4

Updated by O'Neil Delpratt about 1 year ago

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

Bug fix applied in the Saxon 10.9 maintenance release.

Please register to edit this issue

Also available in: Atom PDF