Although I'm not an expert on the xsltc code yet, I do
not believe that the end user can control the inner
workings of xsl:import or xsl:included stylesheets. I
think the compiler looks at all of them by default
when compiling the 'main' stylesheet.
The TrAX API (which both xalan and xsltc use) also
does not by default allow you to separately preprocess
or compile imports/includes from the main stylesheet.
A bunch of this has to do with optimizations and some
of how XSLT was spec'd: it's *much* more difficult for
processors to optimize at all if they can't actually
read the imports/includes when originally processing
the main stylesheet.
That all being said, the Xalan-J 2.x API does support
this to a degree for xalan mode (not xsltc mode),
although Scott or Gary will have to chime in with
details there.
- Shane
=====
<eof aka="mailto:[EMAIL PROTECTED]";
humor="Having fun at JavaOne!" />
__________________________________________________
Do You Yahoo!?
Spot the hottest trends in music, movies, and more.
http://buzz.yahoo.com/
