Actions
Bug #6187
closed
Why is StandardUnparsedTextResolver so insistant that a streaming source be returned?
Start date:
2023-08-26
Due date:
% Done:
0%
Estimated time:
Legacy ID:
Applies to branch:
Fix Committed on Branch:
Fixed in Maintenance Release:
Platforms:
Description
We call the resolver, which can return a Source but we
throw new XPathException("Resolver for unparsed-text() returned non-StreamSource");
if it doesn't get back some flavor of StreamSource.
This seems unreasonable. Consider, for example, the case where this resolves through the XMLResolver. The resolver doesn't return a stream source, it returns a plain old source.
Please register to edit this issue
Actions
.