Community
Participate
Working Groups
The computeFile method of ExtensibleURIResolver does not decode the baseLocation URL before creating the IFile. So if, for instance, the baseLocation is a URL of a filename which contains spaces in it, then a bogus IFile is being created with a filename that contains %20's in it. This leads to errors being thrown in the resolver when it tries to open the resulting invalid IFile.
Doug, To ensure a fix that correctly addresses this scenario can be developed, could you please provide an example/set of steps to reproduce this problem?