XOM API for Processing XML with Java

[Elliotte Rusty Harold <elharo AT metalab.unc.edu>]

At 2:57 PM -0500 6/6/03, Kevin Herrboldt wrote:

> Again, shame on Sun for how they bundled it. And why hasn't the
> Apache group fixed it?

Because they've ditched Crimson in favor of Xerces. Crimson has
effectively been abandoned. Apparently someone at Sun is still
working on Crimson, because I noticed at least one bug get fixed
between 1.4.1 and 1.4.2, but long term Xerces is the way to go.

> Is there any documentation anywhere regarding the efficacy of
> various parsers? Is the order of parsers in Builder based on quality
> of parser? Piccolo is really fast and seems good, but can't
> validate. I'm not sure how good Ælfred is, but it's much, much
> smaller than Xerces.

Roughly. Piccolo would probably be the default for non-validating XOM
were it not for one annoying bug in DOCTYPE handling that breaks
XOM's unit tests. AElfred also has a lot of bugs in handling basic
XML constructs. It's roughly on par with Crimson for quality. Oracle
I don't really know. It's not open source, so I haven't paid a lot of
attention to it. For the moment, Xerces is the only open source
parser that can pass all of XOM's unit tests.
--

  Elliotte Rusty Harold
  elharo AT metalab.unc.edu
  Processing XML with Java (Addison-Wesley, 2002)
  http://www.cafeconleche.org/books/xmljava
  http://www.amazon.com/exec/obidos/ISBN%3D0201771861/cafeaulaitA