Subject: Re: [xsl] 1 condition OK, adding a second blows it up From: Jeni Tennison <jeni@xxxxxxxxxxxxxxxx> Date: Tue, 1 Jul 2003 18:17:29 +0100 |
Hi Allistair, > This works > > <xsl:for-each select="//employee[(./@department = $deptName) and > (./approvals/approval[@timestamp > $filterFDate])]"> > > However, when I add a second condition it fails > > <xsl:for-each select="//employee[(./@department = $deptName) and > (./approvals/approval[(@timestamp > $filterFDate) and (@timestamp < > $filterTDate)])]"> (Obviously the above isn't well-formed XML, so you'll get an error, but you say that escaping the < doesn't help.) The XPath looks OK to me. What do you mean by "fails"? What error do you get, or what does it do differently to what you expect? Cheers, Jeni --- Jeni Tennison http://www.jenitennison.com/ XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
[xsl] 1 condition OK, adding a seco, Allistair Crossley | Thread | RE: [xsl] quick xpath question - us, Wendell Piez |
RE: [xsl] Forcing namespace output/, Passin, Tom | Date | Re: [xsl] xsl:sort in old MSXML, David Carlisle |
Month |