This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Re: Antwort: Re: Indexing a fop generated document.
- To: xsl-list at lists dot mulberrytech dot com
- Subject: Re: Antwort: Re: [xsl] Indexing a fop generated document.
- From: David Carlisle <davidc at nag dot co dot uk>
- Date: Tue, 16 Jan 2001 14:52:53 GMT
- References: <0057440003361725000002L452*@MHS>
- Reply-To: xsl-list at lists dot mulberrytech dot com
>
> <xsl:if
> test="count(//Foundation.Core.Generalization[Foundation.Core.Generalization.c
> hild/Foundation.Core.GeneralizableElement/@xmi.idref=$classID]) > 0">
if used in a boolean context (like test attribute) a node set counts as
true if it is non empty, so there is no need to say
<xsl:if test="count(xxx) > 0">
you can just say
<xsl:if test="xxx>
which is simpler, and may or may not be more efficient depending on
your XSL system.
But in this case it looks like you could just remove the xsl:if as it
isn't doing anything.
If the above test is true, then the following for-each is executed,
if it is not, then it would be executed but would select an empty node
set, so wouldn't do anything.
<xsl:for-each
select="//Foundation.Core.Generalization[Foundation.Core.Generalization.child/Fo
You say
> It only works if the if-test is applied _before_ for-each is
> performed.
but you don't say what doesn't work if you miss out the xsl:if.
David
_____________________________________________________________________
This message has been checked for all known viruses by Star Internet delivered
through the MessageLabs Virus Control Centre. For further information visit
http://www.star.net.uk/stats.asp
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list