That's very strange -- are you absolutely certain the person is using a
pre-compiled stylesheet? There is no way Xalan would reference included
stylesheets from a compiled stylesheet.
I suspect your user _thinks_ he/she is using a compiled stylesheet, but
really isn't. Another strange thing is that a transformation should fail
if the included stylesheet(s) aren't found. Xalan doesn't try to recover
in this case by proceeding without the include(s).
Dave
"Brian Quinlan"
<brian@sweetapp. To: <[EMAIL PROTECTED]>
com> cc: (bcc: David N
Bertoni/Cambridge/IBM)
Subject: RE: Reusing compiled
stylesheets
05/24/2002 01:15
AM
Please respond
to xalan-dev
David wrote:
> You observation is incorrect -- Xalan always processes included and
> imported stylesheets when it compiles the stylesheet. There is a
> post-construction step which "composes" the stylesheets.
Is there a runtime reason why the URIs of the included stylesheets must
be correct, if the root stylesheet is precompiled?
I ask because I got a bug report from a user of my Xalan Python
bindings:
"""Then I tried transforming an XML using the compiled
stylesheet object (compiled) and I got a result that
is relatively short : without the stuff in xsl1, xsl2
... xsl4. [xsl1..xsl4 are included stylesheets]
So I tried to chdir back to /home/cp/work/xsl, and I
do a tranformation to exactly the same XML with
exactly the same "compiled" object, and this time a
much longer result appears, with complete stuff from
templates defined in xsl1 ... xsl4."""
Before I spent a lot of time investigating this problem, I was wondering
if you understand it.
> Take a look at Stylesheet:::postConstruction() to see what's going on.
I took a peek. It definitely does *something* :-)
Cheers,
Brian
