The nodes in a NodeList are not children of the NodeList, so I don't see how they would ever be found by following the child axis.
 
The only explanation I can think of is that I've come across DOM implementations where the same object implements Node in respect of a parent node, and NodeList in respect of its children. (This kind of thing makes programming using dynamic types extremely error-prone!)
 
Please supply sufficient information that I can reproduce and investigate the problem. However, I would expect that when you return a DOM NodeList, it is mapped to an XPath sequence of nodes, so the behaviour you describe as the 9.1 behaviour looks correct to me.

Regards,

Michael Kay
http://www.saxonica.com/
http://twitter.com/michaelhkay



From: Marc Pellmann [mailto:marc.pellmann@inubit.com]
Sent: 24 June 2009 16:18
To: saxon-help@lists.sourceforge.net >> Mailing list for SAXON XSLT queries
Subject: [saxon] Change from 9.0 to 9.1 in org.w3c.NodeList?

Hello!

In an java function, that I call from an XSLT script I give back a org.w3c.NodeList. In Version 9.0 (like in Xalan, too) I could access this in a for-each by method()/* and get all nodes in the list. In 9.1 I need to use method() (without slash and star).

Now I have the problem of different access by Xalan/Saxon.

best regards, marc pellmann