Project

Profile

Help

Actions
Send by e-mail Copy link

Bug #6417

closed

Using xsl:mode on-no-match="skip" gives error Error XTDE0555 but should give XTSE0020

Added by Martin Honnen 7 months ago. Updated about 1 month ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
XSLT Conformance
Sprint/Milestone:
SaxonJS 2.6
Start date:
2024-05-08
Due date:
% Done:

100%

Estimated time:
Applies to JS Branch:
2, Trunk
Fix Committed on JS Branch:
2, Trunk
Fixed in JS Release:
SaxonJS 2.7
SEF Generated with:
Platforms:
Company:
-
Contact person:
-
Additional contact persons:
-

Description

I got sloppy when typing some XSLT 3.0 and ended up with <xsl:mode on-no-match="skip"/>. While Saxon Java just tells me

 XTSE0020  Attribute xsl:mode/@on-no-match must be
  text-only-copy|shallow-copy|deep-copy|shallow-skip|deep-skip|fail

SaxonJS (tested with 2.6/xslt3 command line) gives a very different error

Transformation failure: Error XTDE0555
  No matching template rule for document #13

I think the wrong value for on-no-match should be caught during stylesheet compilation and not as a transformation failure. And that error code XTDE0555 given seems misleading.

Minimal XSLT:

<xsl:stylesheet 
  xmlns:xsl="http://www.w3.org/1999/XSL/Transform" 
  version="3.0"
  exclude-result-prefixes="#all">

  <xsl:mode on-no-match="skip"/>

</xsl:stylesheet>

run with e.g. xslt3 -s:sample1.xml -xsl:test1.xsl against e.g.

<root></root>

gives

Transformation failure: Error XTDE0555
  No matching template rule for document #13
Error XTDE0555
  No matching template rule for document #13
Actions
Copy link
 #4

Updated by Norm Tovey-Walsh 4 months ago

  • Status changed from New to Resolved
  • Applies to JS Branch 2, Trunk added
  • Fix Committed on JS Branch Trunk added

Fixed.

Actions
Copy link
 #5

Updated by Norm Tovey-Walsh 4 months ago

  • Fix Committed on JS Branch 2 added

Also applied to js2 branch

Actions
Copy link
 #6

Updated by Debbie Lockett about 1 month ago

  • Status changed from Resolved to Closed
  • % Done changed from 0 to 100
  • Fixed in JS Release set to SaxonJS 2.7

Bug fix applied in the SaxonJS 2.7 maintenance release.

Please register to edit this issue

Actions
Send by e-mail Copy link

Also available in: Atom PDF Tracking page