Project

Profile

Help

Actions
Send by e-mail Copy link

Bug #4140

closed

Namespace aliasing creating attribute name conflicts.

Added by Michael Kay about 5 years ago. Updated about 5 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Michael Kay
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:
9.9.1.2
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.

Actions
Copy link
 #1

Updated by O'Neil Delpratt about 5 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

Actions
Send by e-mail Copy link

Also available in: Atom PDF