|
From: | Julian Scheid |
Subject: | Re: [Cp-tools-discuss] Re: gjdoc |
Date: | Thu, 06 Feb 2003 03:09:01 +0100 |
User-agent: | Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2) Gecko/20021126 |
Brian Jones wrote:
Julian Scheid <address@hidden> writes: > How far is XSLT integration into Classpath? Pure-Java > XSLT is slower than Xsltproc, but gjdoc would then have > no additional dependencies aside from Classpath and > Classpathx. Use of Xsltproc could be enabled optionally. JAXP from ClasspathX should be arriving shortly, but I don't know if that provides XSLT in the manner you're thinking.
ClasspathX's JAXP implementation doesn't seem to ship with an XSL processor at all. Are there any XSL transformators that we could recommend for linking into the Gjdoc executable when using Gjc? Aside from Gjc, are there any transformators that we could recommend for inclusion in the CLASSPATH, for dynamic linking? Even if ClasspathX does not provide XSLT I would like to get away from the System.exec() call necessary for spawning xsltproc. Given that most JREs today include a JAXP-compatible XSL transformation engine, and that several free engines are available (if not GPLed), I expect it is otherwise unnecessary to have this dependency. Julian
[Prev in Thread] | Current Thread | [Next in Thread] |