A DOM parser, in contrast, typically builds a tree representation of the entire document in memory to begin with, thus using memory that increases with the entire document length.
Another popular use of this term refers to one method of consuming XML data – largely known as Simple API for XML.
One way to avoid these problems is to use an entity resolver (a standard part of SAX) or a URI Resolver (a standard part of JAXP).
•
The following example shows how, in Java, a SAX parser may be created to parse some input source in which the org.apache.xml.resolver.tools.CatalogResolver is used to resolve external entities to locally-cached instances.
This allows applications to access the data in the XML from the object rather than using the DOM or SAX to retrieve the data from a direct representation of the XML itself.
XML | Simple Minds | API | The Simple Life | Simple Plan | Simple Network Management Protocol | 8 Simple Rules | XML Schema (W3C) | XML Schema | Simple Mail Transfer Protocol | Windows API | Simple | Simple API for XML | Blood Simple | ApI | XML schema | XML Information Set | Simple vow | Simple Symphony | Simple Simon | Simple Authentication and Security Layer | Plain Old XML | Home Made Simple | XML database | These Simple Truths | Simple Simon (nursery rhyme) | Charles the Simple | A Simple Plan (film) | A Simple Plan | XML validation |