https://saxonica.plan.io/https://saxonica.plan.io/favicon.ico2020-09-29T06:38:51ZSaxonica Developer CommunitySaxon - Bug #4764: StandardModuleURIResolver can't succeed if its default constructor is usedhttps://saxonica.plan.io/issues/4764?journal_id=164592020-09-29T06:38:51ZNorm Tovey-Walsh
<ul></ul><p>The problem stems from the addition of this test to <code>resolve()</code>:</p>
<pre><code> if (!config.getAllowedUriTest().test(absoluteURI)) {
throw new XPathException("URI scheme '" + absoluteURI.getScheme() + "' has been disallowed");
}
</code></pre>
<p>I don't know if it's sufficient to put a guard around that test (<code>if (config != null) ...</code>) or if that test always needs to work in which case, well, I'm not sure what really.</p> Saxon - Bug #4764: StandardModuleURIResolver can't succeed if its default constructor is usedhttps://saxonica.plan.io/issues/4764?journal_id=166902020-10-27T16:00:26ZMichael Kaymike@saxonica.com
<ul><li><strong>Project</strong> changed from <i>4</i> to <i>Saxon</i></li><li><strong>Category</strong> set to <i>Configuration</i></li><li><strong>Assignee</strong> set to <i>Norm Tovey-Walsh</i></li><li><strong>Priority</strong> changed from <i>Low</i> to <i>Normal</i></li></ul><p>I would suggest</p>
<p>(a) don't do the test if there is no known Configuration (fix needed for 10.x)</p>
<p>(b) after instantiating a ModuleUriResolver, if it extends StandardModuleUriResolver (or conforms to some new to-be-defined interface) then call its setConfiguration() method so it knows the configuration. (this feels more like 11.x)</p> Saxon - Bug #4764: StandardModuleURIResolver can't succeed if its default constructor is usedhttps://saxonica.plan.io/issues/4764?journal_id=167932020-10-29T11:51:56ZNorm Tovey-Walsh
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li></ul> Saxon - Bug #4764: StandardModuleURIResolver can't succeed if its default constructor is usedhttps://saxonica.plan.io/issues/4764?journal_id=169522020-12-01T14:46:31ZNorm Tovey-Walsh
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Resolved</i></li><li><strong>Fix Committed on Branch</strong> <i>10, trunk</i> added</li></ul><p>Per Michael's suggestions:</p>
<p>I've updated the 10.x and trunk so that a missing config doesn't raise an NPE.</p>
<p>In trunk, I've added tests where a <code>ModuleURIResolver</code> is instantiated without a config to provide the config if the instantiated resolver is a <code>StandardModuleURIResolver</code>. This only applies where the resolver is instantiated; it doesn't apply when an already instantiated resolver is passed in from the outside.</p> Saxon - Bug #4764: StandardModuleURIResolver can't succeed if its default constructor is usedhttps://saxonica.plan.io/issues/4764?journal_id=177792021-04-14T15:39:45ZO'Neil Delprattoneil@saxonica.com
<ul><li><strong>Applies to branch</strong> <i>10, trunk</i> added</li></ul> Saxon - Bug #4764: StandardModuleURIResolver can't succeed if its default constructor is usedhttps://saxonica.plan.io/issues/4764?journal_id=177912021-04-14T15:49:36ZO'Neil Delprattoneil@saxonica.com
<ul><li><strong>Status</strong> changed from <i>Resolved</i> to <i>Closed</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>100</i></li><li><strong>Fixed in Maintenance Release</strong> <i>10.5</i> added</li></ul><p>Bug fix applied to Saxon 10.5 maintenance release.</p>