Bug #2454
closed
match="//elname" with mode typed="strict"
Category:
XSLT conformance
Fix Committed on Branch:
9.6
Fixed in Maintenance Release:
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.
A test case match-243 was created for this.
- 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.
- 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.
- 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
- Applies to branch 9.6 added
- Fix Committed on Branch 9.6 added
- Fixed in Maintenance Release 9.6.0.8 added
- Sprint/Milestone set to 9.6.0.8
Please register to edit this issue
Also available in: Atom
PDF