Howdy Al--
Nope.. Absolutely none. 90% of the time, they will be in roughly document-order,
which is defined as the order of the start <tag> when processed sequentially,
with extra rules about where attributes and namespace decls fall (which
we ignore completely).
We're non-conformant on paths that include //, since we're apparently
doing a bredth-first instead of a depth-first walk of the document.
Relatively trivial fix and may even improve efficiency if we move
away from recursion and towards a simple stack-based walk of the tree.
Does that help? What are you actually trying to do?
Anyhow, glad to hear you're not playing with bare metal SAX anymore. :)
-bob
On Wed, 28 Aug 2002, Alan Herod wrote:
> I see that you can get a sorted list when using
> myNode.selectNodes( String xpath, String compXpath )
>
> Is there any guarantee that if I just use
> myDoc.selectNodes( String xpath )
> the resulting order will correlate to the order in the physical XML file?
>
> Thanks, Al
>
--
Bob McWhirter [EMAIL PROTECTED]
The Werken Company http://werken.com/
-------------------------------------------------------
This sf.net email is sponsored by: Jabber - The world's fastest growing
real-time communications platform! Don't just IM. Build it in!
http://www.jabber.com/osdn/xim
_______________________________________________
dom4j-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dom4j-user
