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 off, the templates work correctly.
Unfortunately, company policy regarding software/confidential material
will not allow me to post the input/source I'm using. However, if I
can reproduce the problem in a smaller context, I will open the JIRA bug.
Morris Kwan wrote:
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.
Morris Kwan
XSLT Development
IBM Toronto Lab
Tel: (905)413-3729
Email: [EMAIL PROTECTED]
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 TransformerHandler created from a Templates handler created from a
SAXTransformerFactory.
Now it appears that template priority is not being recognized at all.
We're using Xalan-Java 2.6 on Solaris platform. We are overriding the
default version of Xalan used by the Solaris java command by overriding
the bootclasspath.
Is this a (known) Xalan-Java bug, is there something we have to
change/do to enable template prioritization, do we have to change how
prioritization values are expressed with the SAX components?
--
Edward L. Knoll Phone (FedEx) : (719)484-2717
e-mail (FedEx) : [EMAIL PROTECTED]
e-mail (personal) : [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
