RE: [Classpathx-xml] gnujaxp with JDK1.1.8

[Ma, Steve]

However, in order for this Aelfred2 to be JAXP1.1 compatible, we need to
include the JAXPFactory, which in turn uses XmlReader, and XmlReader needs
pipeline support.  And the chain goes on to include the util directory.

I understand maintaining multiple configuration/distribution is troublesome,
so I'd rather not trouble you for the maintenance except I'd prefer not
modifying any source code because it will make it harder to upgrade.  

Is there a way to make the jar lighter at the same time keeping it JAXP1.1
compatible? 

Thanks,

Steve

-----Original Message-----
From: David Brownell [mailto:address@hidden 
Sent: Friday, December 07, 2001 8:21 PM
To: Ma, Steve
Cc: address@hidden
Subject: Re: [Classpathx-xml] gnujaxp with JDK1.1.8

> Is it possible to release just the AElfred2 parser alone in a jar to
> minimize the size? 

Why don't you just assemble a jarfile with the relevant SAX
code and these two classes?

    - gnu.xml.aelfred2.SAXDriver
    - gnu.xml.aelfred2.XmlParser (internal class)

That won't include the validation support, but that's the core
of AElfred2.   It's only the _optional_ validation support that
brings in any of the pipeline support, and that shouldn't require
that whole package, or anything in "util".  (If it does, please
submit an appropriate patch!)

The deal is that I don't want to get into the business of
trying to maintain multiple configurations/distributions.
Anyone with access to the source code can arrange the
linking to their convenience. Or heck, even with just the
jarfile ... :)

- Dave