(//Menu)[1]ancestor-or-self::Menu/MenuTitulo
That isn't correct Xpath so will generate an error on any conformant
XPath system (I don't know if it would work in wd-xsl, but I didn't
think that had that axis at all)
adding a / so it says:
(//Menu)[1]/ancestor-or-self::Menu/MenuTitulo
would make it syntactically correct but still strange.
(//Menu)[1]
will select a Menu node (or nothing) so ancestor-or-self::Menu will
always be the same as self::Menu so it can be omitted, so the expression
is then equivalent to
(//Menu)[1]/MenuTitulo
David
________________________________________________________________________
This e-mail has been scanned for all viruses by Star. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit:
http://www.star.net.uk
________________________________________________________________________
--~------------------------------------------------------------------
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>
--~--