RE: how do java xsl processors handle xsl:import?

In the case of template rules, Saxon makes no attempt to determine that
particular template rules can never be activated. In general this
requires analysis of patterns to establish whether one pattern subsumes
another. This is trivial of course for simple patterns such as
match="title", but in the general case it's rather difficult.

But this is besides the point anyway. If I were making a concerted
effort to reduce the memory size of the compiled Templates object, there
are probably other things I would do first.

Michael Kay

> -----Original Message-----
> From: owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx 
> [mailto:owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of 
> Robert Koberg
> Sent: 01 December 2003 14:17
> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> Subject:  how do java xsl processors handle xsl:import?
> 
> 
> Hi,
> 
> How do xsl processors handle xsl:import with regard to (don't really 
> know how to say this) storing xsl:templates in a 
> javax.xml.transform.Templates object?
> 
> For sake of example, say I want to xsl:import files that contain 100 
> xsl:templates. The *importing* file overrides all 100 
> xsl:templates with 
> new ones. [I want to cache the javax.xml.transform.Templates 
> object in 
> memory for a webapp]. Will the Templates object contain 200 
> xsl:templates or does it discard the overriden ones?
> 
> thanks,
> -Rob
> 
> 
>  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
> 


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