[jdom-interest] JDOM w/ *long* streams

[Jason Hunter]

> I thought that
> JDOM would provide a higher level interface--already defined--for
> accessing the record data.

JDOM is higher level and easier to use than SAX, but if you need purely
sequential read-only access to large XML data sources, then that's
exactly what SAX was invented for.  JDOM fits the bill when you need
non-sequential access, need the ability to change the doc and/or write
the doc, or want an easier API for accessing the data.

So SAX or JDOM for you?  If JDOM, then you'll need a builder that pulls
data from SAX and makes that data available as needed by JDOM.  You'll
need a special Element subclass and probably a special List
implementation whose get methods are written to pull more data from SAX
if they don't already have the data they need.

-jh-