Hi Bruce,
Bruce D'Arcus wrote:
On Jan 6, 2006, at 9:41 AM, Matthew L. Avizinis wrote:
Also, just now I noticed that in the 2.0 program/classes folder that
_both_ an xt.jar and a xalan.jar are present. You are indicating that
Xalan is now used by default? How can I test/verify this? (OOo xslt
filter debug information is noticeably lacking, i.e. xsl:message or
processor debug dump options, so I'm wondering how this is possible.)
I have two questions about the XSLT support:
The big one is, why is OOo using a Java-based XSLT processor?
At the bibliographic project (of which I am the co-project lead) we have
done a lot of work with XSLT, but it has been suggested to us it is a
bad idea to base production code on XSLT because of the Java dependency.
That seems like a rather big problem to introduce for unclear benefit
(there are C-based alternatives that are equally viable).
Java is used, as the XML filter framework, which uses this processor is
written in Java as well. AFAIK the XML filter framework uses Java as it
originally came from a J2EE enviroment.
And actually, if we're going to use a Java processor, I suggest it ought
to be Saxon, which is not only an excellent XSLT 1.0 processor, but also
adds support for XSLT 2.0.
Was thinking about Saxon as well, but Apache Xerces/Xalan appeared to be
a more 'solid' choice. For example JRE1.4 used Xalan as well.
Any possibility of revisiting this issue then?
Bruce
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
- Svante
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
