At 2003-09-09 15:29 +0100, Thomas Chiverton wrote:
The idea is that we have a node in the input XML to choose what style of
display to use, and then include this, but the xsl:include generates:
org.apache.xml.utils.URI$MalformedURIException: Path contains invalid
character: {

The code looks like:

<xsl:variable name="skin-Config">

        ../skin<xsl:value-of 
select="/report/header/skinInfo/skinFolderName"/>.xsl

</xsl:variable>



<xsl:include href="{$skin-Config}"/>

In the XSLT processing model the *entire* stylesheet has to be processed 
before the processor even looks at the source node file.



There is no way to influence the xsl:include and xsl:import statements by 
the source tree.



You could do a two-step process where in one stylesheet based on the source 
file you configure a new stylesheet fragment that you need and *then* run 
that new synthesized stylesheet fragment on the source file to get your result.



I hope this helps.



......................... Ken



--
Next public European delivery:  3-day XSLT/2-day XSL-FO 2003-09-22
Next public US delivery:        3-day XSLT/2-day XSL-FO 2003-10-13
Instructor-led on-site corporate, government & user group training
for XSLT and XSL-FO world-wide:  please contact us for the details

G. Ken Holman                 mailto:gkholman@xxxxxxxxxxxxxxxxxxxx
Crane Softwrights Ltd.          http://www.CraneSoftwrights.com/s/
Box 266, Kars, Ontario CANADA K0A-2E0    +1(613)489-0999 (F:-0995)
ISBN 0-13-065196-6                       Definitive XSLT and XPath
ISBN 0-13-140374-5                               Definitive XSL-FO
ISBN 1-894049-08-X   Practical Transformation Using XSLT and XPath
ISBN 1-894049-11-X               Practical Formatting Using XSL-FO
Member of the XML Guild of Practitioners:     http://XMLGuild.info
Male Breast Cancer Awareness  http://www.CraneSoftwrights.com/s/bc


XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list