Hello Mr. Kay!
I've found that the scope of URIResolver is not extended to a resolution of external entities and locations in the XInclude.
This limits application of custom uri resolver.
Don't you think it worth to promote this service to a level of parser?
E.g. xerses has a similar api XMLEntityResolver.
The JAXP URIResolver only affects URIs resolved by the XSLT processor. It does not affect the behaviour of the XML parser or of an XInclude processor. That's the job of the SAX EntityResolver.
It would be nice to unify these, but that's a comment on the design of JAXP, not on the Saxon implementation.
Log in to post a comment.
Sign up for the SourceForge newsletter:
You seem to have CSS turned off.
Please don't fill out this field.