RE: [xsl] Traversing nodes and storing a matched value

["Aron Bock" <aronbock@xxxxxxxxxxx>]

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@xxxxxxxxxxxx>
> Reply-To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> To: <xsl-list@xxxxxxxxxxxxxxxxxxxxxx>
> 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@xxxxxxxxx]
> > Sent: 29 June 2005 19:35
> > To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> > 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/