Subject: Re: [xsl] Compound filter in for-each From: Alan Hale <alan.hale@xxxxxxxxxxx> Date: Tue, 24 Mar 2009 22:38:39 +0000 |
At 06:03 PM 3/24/2009, Mike wrote:> .... but if I do this: > > <xsl:for-each > select="Placemark/ExtendedData/Data[@name='rdb_status' and > value='Endangered']"> > > I get no error, but also no data returned -even though there > are matching values.
You haven't shown what you are doing inside the for-each - perhaps that's
where your error is.
How do you know you have now matched the values? What do you get for
count(Placemark/ExtendedData/Data[@name='rdb_status' and value='Endangered'])
Also, you haven't shown us the context (template match) within which the for-each is used, so we don't know if any nodes are actually selected by the path -- even if it's syntactically correct, and plausible to think it might, given what we've seen.
(That's what I meant about "knowing more about what you haven't told us" in my first response. XSLT is easy enough once things line up, but until you know how to make that happen, it'll be mysterious.)
Cheers, Wendell
Michael/Wendell Ah - I see what you mean. Here is the context::
<xsl:for-each select="Placemark"> i.e. with no filter
Alan Hale Aberystwyth
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
RE: [xsl] Compound filter in for-ea, Wendell Piez | Thread | RE: [xsl] Compound filter in for-ea, Michael Kay |
Re: [xsl] copy attribute question, Garvin Riensche | Date | RE: [xsl] copy attribute question, Michael Kay |
Month |