XOM API for Processing XML with Java

["Bradley S. Huffman" <hip AT cs.okstate.edu>]

John Cowan writes:

> Bradley S. Huffman scripsit:
> 
> > But if it's a subclass of ParentNode, it's also a subclass of Node, so I
> > can detach it and try to re-insert it someplace else, which means the
> > core class are going to have to compensate for this special class. Sounds
> > real messy.
> 
> Well, presumably this just falls out from the existing implementation of the
> add-a-child methods, which already have to make this check and throw
> IllegalAddException.

A IllegalAddexception for what? I detached the node and if I test the wrapper
for a instance of Node, it returns true. So it looks like a Node, smells
like a Node, but it's not really like any other Node in the API, so why have
it as a subclass Node or ParentNode? As I said drop the insistence on a query
returning a instance of Nodes and return a List of Objects. In this context,
I just don't see the benefit of forcing users to a subset of the XPath API
by restricting the results to the Nodes class.

Brad