Re: [Cp-tools-discuss] Re: gjdoc

[Nic Ferrier]

Julian Scheid <address@hidden> writes:

> 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.

I'm planning a GCJ based java wrapper for libxml2 (gnome's xml
handling library). The main reason for this is that we don't have an
XSLT processor right now in GNU.


Nic