All the stylesheet modules included in a compilation are merged at
compile time into a single Templates object.
It's a nice idea to separate this into a compilation and a linking
phase, but it would be quite a bit of work, for example it would have a
major impact on the building of the decision tree used for matching
> -----Original Message-----
> From: saxon-help-admin@...
> [mailto:saxon-help-admin@...] On Behalf Of
> Robert Koberg
> Sent: 18 May 2002 22:24
> Cc: saxon-help@...
> Subject: [saxon] caching question
> <just a thought>
> Is there any way to cache included XSLs exclusive of the wrapper XSL?
> For example, I have wrapper_01.xsl that includes one XSL
> (global_definitions.xsl), which in turn includes all of my common
> templates. I might have several different wrapper_n.xsl but only one
> global_definitions.xsl (with all the common templates). Is
> there anyway
> that this common XSL can be cached (behind the scenes??
> programmatically??)? So, the wrapper_n.xsl's get cahched too,
> but they
> include the cached version of global_defs. Am I dreaming?
> I assume every 'wrapper' XSL 're-caches' the include for each
> entry in
> the cache, correct?
> </just a thought>
> Hundreds of nodes, one monster rendering program.
> Now that's a super model! Visit http://clustering.foundries.sf.net/
> saxon-help mailing list
> https://lists.sourceforge.net/lists/listinfo/s> axon-help