XOM API for Processing XML with Java

[Mike Colbert <mbcolbert AT yahoo.com>]

Replying to myself ...
 
I just tried doing parent.indexOf (attribute), which returns -1.  This is 
because XOM doesn't consider attributes to be children of parent nodes.  I 
had not noticed this before.
 
Why is an Attribute a Node that has a ParentNode as a parent, as returned by 
attribute.getParent(), but at the same time it's not a child of a ParentNode, 
as returned by parent.getChild(n)?
 
Mike


----- Original Message ----
From: Mike Colbert <mbcolbert AT yahoo.com>
To: Michael Kay <mike AT saxonica.com>; xom-interest AT lists.ibiblio.org
Sent: Wednesday, March 15, 2006 10:07:32 AM
Subject: Re: [XOM-interest] Query: Any way to determine ordering of twonodes?


Ah, of course.  I haven't personally tried doing a parent.indexOf (attribute) 
and the javadoc doesn't really get into what happens in that case.  I presume 
its stable and repeatable, but I would verify that before betting on it.  In 
any case, good thinking.  I'm sure there are other special cases I haven't 
thought of.  Interesting problem, though.

Mike


----- Original Message ----
From: Michael Kay <mike AT saxonica.com>
To: Mike Colbert <mbcolbert AT yahoo.com>; xom-interest AT lists.ibiblio.org
Sent: Wednesday, March 15, 2006 9:03:08 AM
Subject: RE: [XOM-interest] Query: Any way to determine ordering of twonodes?


Attribute nodes don't have an intrinsic ordering: you have to invent an
arbitrary ordering and make sure it's applied consistently.

Namespace nodes often have only a transient physical existence since most
models store namespace declarations rather than namespace nodes; but you
still need to devise a stable and repeatable ordering.

Michael Kay
http://www.saxonica.com/ 
_______________________________________________
XOM-interest mailing list
XOM-interest AT lists.ibiblio.org
http://lists.ibiblio.org/mailman/listinfo/xom-interest