Oh, I didn't know that ... I use xalan, and it must be more permissive.
To the OP: you could work around this by explicitly selecting relevant menu
in the call to write-menu.
--A
From: "Michael Kay" <mike(_at_)saxonica(_dot_)com>
Reply-To: xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
To: <xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com>
Subject: RE: [xsl] Traversing nodes and storing a matched value
Date: Wed, 29 Jun 2005 19:52:24 +0100
XSLT 1.0 doesn't allow variables to be used in a match pattern.
Michael Kay
http://www.saxonica.com/
> -----Original Message-----
> From: Mat Bergman [mailto:matbergman(_at_)yahoo(_dot_)com]
> Sent: 29 June 2005 19:35
> To: xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
> Subject: RE: [xsl] Traversing nodes and storing a matched value
>
> This looks like a most elegant solution. One
> head-scratching error occurs when I play with it using
> the MSXML processor:
> Variables may not be used within this expression.
> menu[not(existes = -->$siteID<--)]
>
> When I hard-code the value in place of the variable,
> it works fine. Am I missing something?
>
> Thanks,
>
> -Mat
_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today - it's FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
--~------------------------------------------------------------------
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>
--~--