Subject: 1 condition OK, adding a second blows it up
From: "Allistair Crossley" <Allistair.Crossley@xxxxxxx>
Date: Tue, 1 Jul 2003 17:19:56 +0100
|
Another one that has caused me grief..
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)])]">
as does this permutation
<xsl:for-each select="//employee[(./@department = $deptName) and (./approvals/approval[@timestamp > $filterFDate]) and (./approvals/approval[@timestamp < $filterTDate])]">
$filterFDate and $filterTDate are both defined. The escaped versions of < and > also fail.
Allistair Crossley
Senior Intranet Developer
QAS Ltd
Direct Dial: 020 7819 5343
<FONT SIZE=1 FACE="VERDANA,ARIAL" COLOR=BLUE>
-------------------------------------------------------
QAS Ltd.
Developers of QuickAddress Software
<a href="http://www.qas.com">www.qas.com</a>
Registered in England: No 2582055
Registered in Australia: No 082 851 474
-------------------------------------------------------
</FONT>
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
|
Cart
