"Your typical node-set" by definition does not guarantee that you'll
have sibling nodes, or even nodes belonging to a single xml document.
Certainly, this is engine-independent, has nothing to do with "the
.NET architecture" and is a basic XPath concept.
--
Cheers,
Dimitre Novatchev
---------------------------------------
To avoid situations in which you might make mistakes may be the
biggest mistake of all.
On 11/30/05, Ian E. Powell <Ian(_dot_)Powell(_at_)mdbuyline(_dot_)com> wrote:
Following up. David was correct in that the .NET architecture was not
providing your typical nodeset to the
XSLT. The System.Xml.XPath.XPathNodeIterator was essentially providing a
"windowPane" view of the original document
through the $services parameter. Using the generate-id() showed
this.(Not explicitly mentioned on MSDN that I could find).
Changing preceding-sibling() to preceding() solved the problem.Thanks
for pointing me in the right direction on this one
David.
Ian
_________________________________________________________________
This message is for the designated recipient only and may contain
privileged, proprietary, or otherwise private information. If you
have received it in error, please notify the sender immediately
and delete the original. Any other use of the email by you is
prohibited.
_________________________________________________________________
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail:
<mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--