Project

Profile

Help

Bug #3460

closed

XQDY0025 (duplicate attribute) reported under XSLT (with docbook)

Added by Michael Kay over 6 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
XSLT conformance
Sprint/Milestone:
-
Start date:
2017-09-26
Due date:
% Done:

100%

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

Description

Reported on the saxon-help forum here:

https://saxonica.plan.io/boards/3/topics/6990

Reproduced (occurs only on 9.7, with bytecode enabled: fixed in 9.8)

We have upgraded Saxon-EE from 9.6 to 9.7.0.20. Then while performing XSLT transform, we started bumping into this fatal error:

Error on line 206 column 49 of table.xsl:

XQDY0025: Cannot create an element having two attributes with the same name: @width

at xsl:call-template name="adjust-column-widths"

Do I understand correctly that "XQDY0025" is an XQuery error and isn't supposed to occur during an XSLT transform?

We are using a customized flavor of DocBook5 and XSLT2.0. I tried running the XSLT transform with the same DocBook and XSLT files in oXygen 19.0 (which uses Saxon-EE 9.7.0.15), but haven't seen an error.

Actions #1

Updated by Michael Kay over 6 years ago

The problem occurs because in generated bytecode there are various calls to allocateSequenceOutputter() that supply an incorrect value for the third argument, which is an integer language code used to distinguish XSLT from XQuery behaviour. These were fixed on the 9.8 branch before release (on 2017-05-24). The code was correct back in 2014, I can't see why the error would have been introduced.

Actions #2

Updated by Michael Kay over 6 years ago

  • Status changed from New to Resolved
  • Fix Committed on Branch 9.7 added

Patch committed and tested (on the 9.7 branch only)

Actions #3

Updated by O'Neil Delpratt over 6 years ago

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

Bug fix applied in the Saxon 9.8.0.5 maintenance release.

Please register to edit this issue

Also available in: Atom PDF