And maybe even more interesting might be an understanding of the team
and the procedures that govern currently XSLT development for JDK... Has
anyone any ideas on that?
Regards,
Sergey Ushakov
On 08.04.2019 07:56, Mukul Gandhi wrote:
A minor thought, about this topic.
On Tue, Feb 19, 2019 at 11:45 AM Mukul Gandhi <[email protected]
<mailto:[email protected]>> wrote:
Oracle JDK's 11.0.2 XSLT processor produces following result,
ERROR: 'line 7: Unsupported XSL element 'template1'.'
FATAL ERROR: 'line 7: Unsupported XSL element 'template1'.'
javax.xml.transform.TransformerConfigurationException: line 7:
Unsupported XSL element 'template1'.
at
java.xml/com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl.newTemplates(TransformerFactoryImpl.java:1061)
at
java.xml/com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl.newTransformer(TransformerFactoryImpl.java:817)
at XSLTTest.main(XSLTTest.java:12)
(this clearly shows that, Oracle Java 11 XSLT processor is based
on Xalan, and by default it uses Xalan's XSLTC mode)
Instead of having above test case, to know which XSLT processor the
JDK contains, following seems to be a far simple method.
Only with the following code (and with no other Xalan distribution in
the classpath),
TransformerFactory tf = TransformerFactory.newInstance();
System.out.println("TransformerFactory implementation: " +
tf.getClass().getName());
Oracle's JDK 11.0.2 prints,
TransformerFactory implementation:
com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl
That is its sure that, Oracle's JDK 11 contains a XSLT processor
derived from Xalan. But I don't know, what are all the differences
between Oracle JDK's Xalan and the XalanJ hosted at xalan.apache.org
<http://xalan.apache.org>. With some of my readings recently, I think
that XSLT processor available within Oracle's JDK contains few changes
& bug fixes as compared to the XalanJ hosted at xalan.apache.org
<http://xalan.apache.org>.
--
Regards,
Mukul Gandhi
