Re: Add jar files to classpath in VAJ?

["David Morris" <dmorris@xxxxxxxxxxxxx>]

Bruce,

As far as I know Crimson, which used to be Sun's parser, does not implement
JAXP and is being replaced by Xerces.  XML4J is IBM's version of Xerces and
is supposed to be more stable but it lags behind Xerces. It is dangerous to
mix various parsers or you may end up doing some debugging.  I have been
using Xerces 1.4+ for a while now and have not had any problems. I am also
using Xalan 2_2_D9, which has a problem compiling one of its inner class in
VAJ, but it is unlikely you will need that class.

To get this to work you also need to get the latest W3C DOM classes.  You should
be able to pull them out of the Xalan distribution in one of the Jar files.  
Also, you
may need javaCup and another BCEL package.  I could get you the URL's or just
email them to you if you want.

David Morris

>>> brucej@mrc-productivity.com 08/30/01 02:57PM >>>
 One thing good about standard (JAXP) is that at code level I don't have
concern about what I am using: crimson or xerces or others (for parsing).
For transformation too the code is the same for xalan or saxon or others as
long as they implement JAXP/TrAX. Also my understanding is that JAXP is just
interfaces/abstract classes for others to implement and it is thin.
 Bruce

----- Original Message -----
From: "Joe Pluta" <joepluta@PlutaBrothers.com>
To: <java400-l@midrange.com>
Sent: Thursday, August 30, 2001 11:26 AM
Subject: RE: Add jar files to classpath in VAJ?


> I did a little more looking.  The class you are using comes from the JAXP
> 1.1.1 specification.  This is part of J2EE1.3 and will be included in
> J2SE1.4.  To use it with VAJ, you probably need to import jaxp.jar,
> xalan.jar, and crimson.jar.  I've never done it, so I can't be much help.
I
> decided not to use the standard XML stuff once I realized how fat the
> standard XML implementations were (and they need to be, to handle all the
> possibilities of XML).  Instead, I wrote my own parser.
>
> Joe