> Okay, but all of the templates were imported. The template it
eventually selected to execute
> was also an imported template. Why did it select imported template B
with a lower priority
> versus imported template C? The one it ultimately selected was the
last template imported;
> I moved t
>...Why did it select imported template B with a lower priority versus
imported template C?
If they were imported from different places, then their import precedence
differs. But it appears that you really want to switch over to
xsl:include, since you want to avoid the effects of import precede
Okay, but all of the templates were imported. The template it
eventually selected to execute was also an imported template. Why did
it select imported template B with a lower priority versus imported
template C? The one it ultimately selected was the last template
imported; I moved them aro
Edward Knoll writes:
>The templates at issues are actually distributed across multiple files.
>A master XSL file references these templates using . If I
>change the to an , the prioritization works.
>...should I expect this behavior?
Yes, import precedence outweighs template priority. We have a
Yes, you should expect that behavior.
Include treats the other file as part of the same stylesheet source
document. Import brings it in at reduced priority -- "lower Importance", if
you need a mnemonic. See the XSLT spec for details.
__
Joe Kesselman, IBM N
The templates at issues are actually distributed across multiple files.
A master XSL file references these templates using . If
I change the to an , the prioritization works.
I've never been entirely sure of the difference between xsl:import and
xsl:include, should I expect this behavior?
Please disregard this. A misedited file appeared to resolve the
problem; taking the mode attribute off did not fix the problem.
Edward L. Knoll wrote:
I have isolated the problem further: the templates where priorities
are not working also have mode attributes. If I take the mode
attributes
I have isolated the problem further: the templates where priorities are
not working also have mode attributes. If I take the mode attributes
off, the templates work correctly.
Unfortunately, company policy regarding software/confidential material
will not allow me to post the input/source I'm
I believe template priority should work in all modes of transformation,
without any code change from the user side. Please open a bug in the JIRA
database (http://nagoya.apache.org/jira/secure/Dashboard.jspa) and attach
the input xml, stylesheet and the Java code to reproduce the problem.
Morr
We have a XSL stylesheet which has prioritized templates. It was
working as expected when we were using org.apache.xalan.xslt.Process to
process it. We've since changed our processing to be handled by a
chain of SAX content handlers with the core XSL processing being handled
by a Transformer
10 matches
Mail list logo
