[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Classpathx-xml] Errors building GNU JAXP 1.1 with Cygwin

From: Andy Madigan
Subject: Re: [Classpathx-xml] Errors building GNU JAXP 1.1 with Cygwin
Date: Wed, 27 Oct 2004 14:54:01 -0700 (PDT)

I've taken a look at the XT code, I'm not entirely sure that the
processor could be used with a JAXP binding (I ran into a brick wall
while trying to do this, I couldn't find a way to control URI
resolution) without a lot of reworking. Using a native processor seems
OK for now, but portability is an issue. I ran into this problem and
wrote a couple of interfaces that essentially represented the subset of
JAXP I use (and then implemented the interfaces for XT), so I can
quickly switch out the impls once a better processor is available.  If
somebody else sees a way to bind XT directly to JAXP, that would at
least make it portable and simple, but I wouldn't put too much time
into it. Any time devoted to XT would be better spent on a new
processor. As for XT + GPL (this is answered in an earlier e-mail as
well), I think that the license is the MIT license.
--- Chris Burdess <address@hidden> wrote:

> Phil Shaw wrote:
> > Thanks, I reached that limit pretty early on! For the time being I 
> > have extracted a pure Java sub-set of GNU JAXP, which is enough for
> > my immediate requirements.
> Adding a configuration option to the build system to make libxmlj
> optional is on my to-do list.
> > Incidentally, the gnu.xml.dom.ImplementationSource class has an 
> > awkward dependency on gnu.xml.libxmlj.
> I know, this should really be dynamic.
> > I'll come back to libxmlj in due course, but I'd rather find an XSL
> > solution that is truly portable (and GPL).
> As far as I am aware, there isn't one (in Java). It's on the roadmap
> for
> GNU JAXP - I've recently introduced an XPath engine which is a
> critical
> component - but it is a nontrivial amount of work and may take some
> time. Volunteers would be welcome, of course!
> > I suppose the terms for 
> > James Clark's XT processor are incompatible with GPL?
> I don't know, you'd have to ask address@hidden
> > Must we have 
> > all copyright assigned to FSF?
> In ClasspathX this is not required, but GNU JAXP will probably become
> part of the Classpath project which does require copyright
> assignment.
> -- 
> Chris Burdess
> _______________________________________________
> Classpathx-xml mailing list
> address@hidden


reply via email to

[Prev in Thread] Current Thread [Next in Thread]