Project

Profile

Help

Bug #2454

closed

match="//elname" with mode typed="strict"

Added by Michael Kay over 9 years ago. Updated about 9 years ago.

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

100%

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

Description

When <xsl:mode typed="strict"/> is used, a template with a match pattern of the form match="//element-name" is not treated as match="//schema-element(element-name)" as it should be. This means there is no error if no schema declaration of the element is found, and no static type-checking of paths found in the body of the template.

Actions #1

Updated by Michael Kay about 9 years ago

A test case match-243 was created for this.

Actions #2

Updated by Michael Kay about 9 years ago

  • Status changed from New to Rejected

Tests match-243 and match-244 appear to be working, so I am closing the bug with no action.

Actions #3

Updated by Michael Kay about 9 years ago

  • Status changed from Rejected to Resolved

I'm not entirely sure of the history of this, but I have found uncommitted changes to the 9.6 code connected with this issue, and they appear to make sense (And are aligned with tested 9.7 code), so I am committing the changes.

Actions #4

Updated by O'Neil Delpratt about 9 years ago

  • Status changed from Resolved to Closed
  • % Done changed from 0 to 100
  • Fixed in version set to 9.6.0.8

Bug fix applied in the Saxon 9.6.0.8 maintenance release

Actions #5

Updated by O'Neil Delpratt about 9 years ago

  • Applies to branch 9.6 added
  • Fix Committed on Branch 9.6 added
  • Fixed in Maintenance Release 9.6.0.8 added
Actions #6

Updated by O'Neil Delpratt about 9 years ago

  • Sprint/Milestone set to 9.6.0.8

Please register to edit this issue

Also available in: Atom PDF