Actions
Bug #6230
closed
fn:transform doesn't use the resource resolver from the XPathContext
Status:
Resolved
Priority:
Low
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
2023-10-24
Due date:
% Done:
0%
Estimated time:
Legacy ID:
Applies to branch:
10, 11, 12, trunk
Fix Committed on Branch:
11, 12, trunk
Fixed in Maintenance Release:
Platforms:
Description
If an XPath expression is evaluated, and that expression calls fn:transform, the implementation of fn:transform creates a new Xslt30Transformer to run the transformation.
But that Xslt30Transformer doesn't inherit the resource resolver from the XPath context on the XPathSelector used to evaluate the expression. That seems like a bug.
Updated by Norm Tovey-Walsh about 1 year ago
- Fix Committed on Branch 12, trunk added
Fixed on 12 and trunk.
Updated by Norm Tovey-Walsh about 1 year ago
- Status changed from New to Resolved
I also added a unit test based on Martin's test case from the help forum. (Thank you, Martin!)
Updated by O'Neil Delpratt about 1 year ago
- Fixed in Maintenance Release 12.4 added
Bug fix applied in the Saxon 12.4 Maintenance release. Leaving it marked as 'Resolved' until fix applied on Saxon 11.
Updated by Norm Tovey-Walsh 6 months ago
- Fix Committed on Branch 11 added
Ported the change back to the 11 branch in case we ever do another release of that branch.
Please register to edit this issue
Actions
.