Bug #5595
closed
Saxon 11 - error when using wrapper over ResourceResolverWrappingURIResolver
0%
Description
I'm using a ResourceResolverWrappingURIResolver over "org.apache.xml.resolver.tools.CatalogResolver" The method "org.apache.xml.resolver.tools.CatalogResolver.resolve(String, String)" always returns a SaxSource. This makes the Saxon StandardUnparsedTextResolver.resolve(URI, String, Configuration) to break with an error as it only supports StreamSource. I would suggest automatically converting the SaxSource to a StreamSource in the "StandardUnparsedTextResolver.resolve" method to handle such cases.
Related issues
Updated by Michael Kay almost 2 years ago
- Is duplicate of Bug #5582: External resolver library returns SAXSource which StandardUnparsedTextResolver rejects added
Updated by Michael Kay almost 2 years ago
- Status changed from New to Duplicate
- Platforms Java added
As it happens I'm working on this one right now.
Updated by Michael Kay almost 2 years ago
On which object (XsltCompiler, XsltTransformer, etc) are you setting the resolver?
Updated by Radu Coravu almost 2 years ago
Sorry for posting a duplicate. I'm doing a net.sf.saxon.Configuration.setResourceResolver(ResourceResolver) using a ResourceResolverWrappingURIResolver.
Please register to edit this issue
.