[xsl] Re: Re: [xsl] Importing compiled stylesheets
"Dimitre Novatchev" <[email protected]>
| Newsgroups | gmane.text.xml.xslt.extensions,gmane.text.xml.xsl.general.mulberrytech |
|---|---|
| Message-ID | <[email protected]> |
On 6/13/05, Jirka Kosek <[email protected]> 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 --~------------------------------------------------------------------ XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/ or e-mail: <mailto:[email protected]> --~--