XOM API for Processing XML with Java

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

Bradley S. Huffman wrote:


> What's the problem with #1?  If you offer no public constructors or
> setters, and don't allow it to be detached what current code would
> need to be reconsidered?

They're a lot of methods that take nodes as arguments throughout the API 
ranging from ParentNode.insertChild() to XOMTestCase.assertEquals(). I 
don't really relish going through the whole API looking at each and 
every one of them to figure out what would happen if an 
XPathNamespaceNode were passed to it. :-(

--
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