skip to content »

Updating xml using java

You can configure the DOM with different access patterns such as read-only, streaming, transient update, and shadow copy, achieving maximum memory use and performance in your applications.Unlike DOM, SAX is event-based, so it does not build in-memory tree representations of input documents.

If the XML document does conform, then the document is valid, which means that the structure of the document conforms to the DTD or schema rules.A nonvalidating parser checks for well-formedness only.Table 4-1 shows the flags that you can use in You can use the XML compressor, which is implemented in the XML parser, to compress and decompress XML documents.For the scalable DOM, the configuration and creation are mainly supported using the interfaces.Using pluggable DOM, XML data can be easily moved from one processor to another.This chapter assumes that you are familiar with the following technologies: JAXP version 1.2 includes an XSLT framework plus some updates to the parsing API to support DOM Level 2 and SAX version 2.0 and an improved scheme to locate pluggable implementations.

JAXP provides support for XML schema and an XSLT compiler.

The main disadvantage of JAXP is that it runs more slowly than vendor-specific APIs.

In addition, several features are available through Oracle-specific APIs that are not available through JAXP APIs.

In general, the DOM API provides the following advantages: Release 1 (11.1), XDK provides scalable, pluggable support for DOM.

This relieves problems of memory inefficiency, limited scalability, and lack of control over the DOM configuration.

The degree of compression depends on the type of document: the larger the tags and the lesser the text content, the better the compression.