Re: [xsl] Bizarre problem with MSXML4 that doesn't happen in MSXML3

Subject: Re: [xsl] Bizarre problem with MSXML4 that doesn't happen in MSXML3
From: David Carlisle <davidc@xxxxxxxxx>
Date: Fri, 11 Apr 2003 17:51:26 +0100
Probably unrelated to your problem but this looks very suspicious code


  <xsl:when test="boolean(/object/securityacl)=true">


If there is a /object/securityacl element then this will compare the
string "true" with the string value of a <true> element child of the
current element. If there is no such <true> element, the test will be
false. 

If there is not a /object/securityacl element then it will compare 
the string "false" with the string value of a <true> element child of the
current element. If there is no such <true> element, the test will be
false.

Is that really what was intended?

I suspect that you intended

<xsl:when test="/object/securityacl">

which is true just if there is an /object/securityacl element.

Similarly

<xsl:when test="count(object/data/row) > 0">

implies finding all the rows and counting them (unless your system
optimises this expression for you)

<xsl:when test="object/data/row">

is the same test but probably more likely to be optimised.

David

________________________________________________________________________
This e-mail has been scanned for all viruses by Star Internet. 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


Current Thread