[XALANJ-2332] If a URIResolver is provided, don't call SystemIDResolver.getAbsoluteURI in document() function

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 2.7.1, 2.7, 2.6
• Fix Version/s: The Latest Development Code
• Xalan info: PatchAvailable
• Assignee: Brian Minchau
• Reporter: Nicholas Sushkin
• Reviewer: Christine Li
• Created: 01/Nov/06 02:05
• Updated: 11/Dec/07 15:02

Description

If the user provides a URIResolver that returns the Source given the absolute URI of the stylesheet module doing the include/import and the relative URI from the href attribute, and if that Source has its system ID set, then there is no reason for the XSLT processor to get involved with the contents of the URIs. The user has provided the full management of stylesheet URIs, to resolve all included/imported Source stylesheet modules and their absolute URIs.

The URIs are supposed to be legitimate URIs, but wheter or not they actually are should be in the user's control. For example the URIs might be of the form "file:///..." with directories or filenames that have characters in them that are not allowed in legitimate URIs.

On the other hand, if the user hasn't provided a URIResolver, or that resolver doesn't return a Source, or that Source doesn't have its system ID set, then the fallback of using SystemIDResolver to get the base URI of the included document is OK. If the URIs are not legitimate, the services provided by this class may throw MalformedURIException.

Issue Links

• is a clone of: XALANJ-2205 If a URIResolver is provided, don't call SystemIDResolver.getAbsoluteURI