Actions
Bug #5409
closed![Author: Michael Kay](https://www.gravatar.com/avatar/db6526d63053f09b62e52c2da8b2230a?rating=PG&size=50&default=https%3A%2F%2Fassets.plan.io%2Fimages%2Fdefault_avatar.png)
![Assignee: Michael Kay](https://www.gravatar.com/avatar/db6526d63053f09b62e52c2da8b2230a?rating=PG&size=22&default=https%3A%2F%2Fassets.plan.io%2Fimages%2Fdefault_avatar.png)
xsl:message document is not available as $err:value
Start date:
2022-03-19
Due date:
% Done:
100%
Estimated time:
SEF Generated with:
Platforms:
Company:
-
Contact person:
-
Additional contact persons:
-
Description
Section 8.3 of the XSLT 3.0 spec states that if the error arising from <xsl:message terminate>
is caught using try/catch, then the document node holding the error message constructed by xsl:message should be available in the catch block as $err:value. This is not happening.
Test case message-0501 fails as a result, with either compiler.
Fixed in the code of Expr["message"].
Updated by Debbie Lockett about 2 years ago
- Status changed from Resolved to Closed
- % Done changed from 0 to 100
- Fixed in JS Release set to SaxonJS 2.4
Bug fix applied in the SaxonJS 2.4 maintenance release.
Please register to edit this issue
Actions
Also available in: Atom PDF Tracking page