[
https://issues.apache.org/jira/browse/XALANJ-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brian Minchau closed XALANJ-2205.
---------------------------------
closing this issue.
> If a URIResolver is provided, don't call SystemIDResolver.getAbsoluteURI
> ------------------------------------------------------------------------
>
> Key: XALANJ-2205
> URL: https://issues.apache.org/jira/browse/XALANJ-2205
> Project: XalanJ2
> Issue Type: Bug
> Affects Versions: 2.7
> Reporter: Brian Minchau
> Assignee: Brian Minchau
> Fix For: 2.7.1
>
> Attachments: ProcessorInclude.patch4.txt
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
