Actions
Bug #5311
closed
StackOverflow involving resolvers
Start date:
2022-02-11
Due date:
% Done:
100%
Estimated time:
Legacy ID:
Applies to branch:
11, trunk
Fix Committed on Branch:
11, trunk
Fixed in Maintenance Release:
Platforms:
Updated by Michael Kay about 2 years ago
The issue here is that the user-supplied configuration-level resolver delegates to the StandardURIResolver, which in turn delegates to the user-supplied configuration-level resolver.
I'm not sure how realistic this problem is, but on balance, I think it's probably better if the StandardURIResolver falls back to the DirectResourceResolver.
Note that the StandardURIResolver only really exists in 11.x for backwards compatibility, because user-written URIResolvers are likely to extend it or delegate to it.
Updated by Michael Kay about 2 years ago
- Category set to Internals
- Status changed from New to Resolved
- Applies to branch 11, trunk added
- Fix Committed on Branch 11, trunk added
Fixed by changing StandardURIResolver so it delegates to the DirectResourceResolver only.
Updated by Debbie Lockett about 2 years ago
- Status changed from Resolved to Closed
- % Done changed from 0 to 100
- Fixed in Maintenance Release 11.2 added
Bug fix applied in the Saxon 11.2 maintenance release.
Please register to edit this issue
Actions
.