XOM API for Processing XML with Java

[John Cowan <cowan AT ccil.org>]

Elliotte Rusty Harold scripsit:

> OK. I think I see. It's basically a replace method, right? And it 
> differs from insert in that it doesn't shift the position of the 
> other nodes?

Correct.

> I'll need to think about this more deeply when my brain is less fuzzy 
> than it is now. To be honest, I wasn't incredibly thrilled by adding 
> insert and remove, but they turned out to be very useful for XInclude.

The utility of this is that it lets people construct their own Nodes
objects and stuff their own nodes in them as they please.  You can use
it as a queue or stack of nodes, or you can have a method that accepts
a Nodes argument, does something with each node, and replaces it with
a new node.

Similar tricks can be played with Element if putChild and putAttribute
are added; they have the same semantics as Node.put.

Essentially, Nodes and Element can function as useful collection classes
for specialized content.

-- 
"By Elbereth and Luthien the Fair, you shall    jcowan AT reutershealth.com
have neither the Ring nor me!"  --Frodo         http://www.ccil.org/~cowan