[
https://issues.apache.org/jira/browse/SYNAPSE-489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Veithen resolved SYNAPSE-489.
-------------------------------------
Resolution: Fixed
Fix Version/s: 1.3
Added support for the <resource> element (cf. <publishWSDL>) in the XSLT
mediator. This allows to resolve xsl:import and xsl:include from the repository
and should be enough for Synapse 1.3. For the next release we should implement
a more sophisticated resolver framework that would allow to resolve relative
URIs directly from the repository.
> base URI for XSLT include/import
> --------------------------------
>
> Key: SYNAPSE-489
> URL: https://issues.apache.org/jira/browse/SYNAPSE-489
> Project: Synapse
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.2
> Environment: Windows XP 2002 SP2
> JDK 1.5.0_09
> Xalan 2.7.0
> Reporter: mikhailfranco
> Assignee: Andreas Veithen
> Priority: Minor
> Fix For: 1.3
>
>
> I have an XSLT which includes another stylesheet,
> e.g. main.xsl has this line:
> <xsl:include href="math.xsl"/>
> and the XSLT mediator refers to the main stylesheet in the local registry:
> <localEntry key="XSL_main" src="file:///C:/foo/bar/xsl/main.xsl"/>
> ...
> <xslt key="XSL_main"/>
> When the transform runs I get these errors:
> SystemId Unknown; Line #6; Column #34; Had IO Exception with stylesheet
> file: math.xsl
> The included file math.xsl is in the same directory as main.xsl, and
> xsl:include with a relative URL should be resolved relative to the including
> document base URI, but obviously the XSLT processor cannot find it.
> Synapse should set the main XSLT file URI as the System ID on the JAXP XSLT
> processor source, so the import/includes are resolved correctly.
> Workaround is to put all the included XSLTs in the SYNAPSE_HOME directory,
> or convert all the import/includes to absolute URLs.
--
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]
