Altova Mailing List Archives


[xsl] Re: [exslt] Re: [xsl] Importing compiled stylesheets

From: Dimitre Novatchev <dnovatchev@--------->
To:
Date: 6/13/2005 11:11:00 AM
On 6/13/05, Jirka Kosek <jirka@xxxxxxxx> wrote:
> Dimitre Novatchev wrote:
>
> > Then this is certainly a good candidate for:
> >
> >      <exslt:include-compiled-module href="hrefToCompiledStylesheet"/>
> >
> >
> > Any opinions from the exslt mailing list?
>
> Wouldn't it be better to create custom attribute for xsl:include. Like:
>
> <xsl:include href="uncompiled.xsl"
>              exsl:compiledStylesheetLocation="hrefToCompiledStylesheet"/>
>
> That way you will get compatibility with all XSLT processors and
> performance boost in ones that will support
exsl:compiledStylesheetLocation.
>
>                                        Jirka

I think that Michael Kay explained why xsl:include is not appropriate
to use for compiled stylesheet modules -- just re-read his first reply
in this thread (in the xsl-list).

A compiled module will need to be defined as something more closed. It
may be a collection of many compiled stylesheets. What is important is
its property that it doesn't use/know about global objects that exist
outside this module (such as global variables, keys, etc). The only
way to pass information to this module is by using parameters.


Cheers,
Dimitre Novatchev

Disclaimer

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.