Project

Profile

Help

Bug #4140

Namespace aliasing creating attribute name conflicts.

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

Status:
Closed
Priority:
Normal
Assignee:
Category:
XSLT conformance
Sprint/Milestone:
-
Start date:
2019-02-20
Due date:
% Done:

100%

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

Description

See spec bug 30400. The spec doesn't say what happens if namespace aliasing causes two attributes on a literal result element to have the same name. Saxon currently outputs one of them and ignores the other. A better solution is to report a static error. See test case namespace-alias-1909.

I have added the error check to LiteralResultElement.java on the 9.9 branch and trunk.

History

#1 Updated by O'Neil Delpratt over 2 years ago

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

Bug issue fixed in the Saxon 9.9.1.2 maintenance release.

Please register to edit this issue

Also available in: Atom PDF