XOM API for Processing XML with Java

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

Wolfgang Hoschek wrote:

> Adjacent text nodes probably don't come up often when assembling a XOM 
> tree in memory, and I speculate that they also rarely comes up when 
> getting a document from a (SAX) Builder.

They shouldn't come up at all when assembling a document from a builder. 
 Probably the most common case where you get them is when you delete an 
element/comment/processing instruction that sites between two text nodes.

I'm not willing to except that we just have to break XPath here. I think 
 it's possible to make this work without auto-coalescing all text 
nodes. It's just going to require an additional level of indirection.

--
Elliotte Rusty Harold  elharo AT metalab.unc.edu
XML in a Nutshell 3rd Edition Just Published!
http://www.cafeconleche.org/books/xian3/
http://www.amazon.com/exec/obidos/ISBN=0596007647/cafeaulaitA/ref=nosim