This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
RE: Nesting for-each elements - Can it be done?
- To: "'xsl-list at lists dot mulberrytech dot com'" <xsl-list at lists dot mulberrytech dot com>
- Subject: RE: [xsl] Nesting for-each elements - Can it be done?
- From: Chuck Evans <chuck dot evans at click2learn dot com>
- Date: Thu, 16 Aug 2001 17:34:05 -0700
- Reply-To: xsl-list at lists dot mulberrytech dot com
Thank you very much for your help. I'll update the processor as soon as
possible and will look into using apply-templates as you suggest. Maybe this
is another newbie question, but will the new processor work under
Win2K/IIS5? I'm guessing it will, but it never hurts to ask.
Chuck Evans
-----Original Message-----
From: Chris Eckert [mailto:ceckert@bendcable.com]
1. First, update the MSXML processor to the XSLT compliant version. See the
FAQ at http://www.netcrucible.com/xslt/msxml-faq.htm.
This isn't why your transformation is failing, but most subscribers to the
list use XSLT (not the MS specific dialect TR-WD)
2. The 2nd for-each is not matching any elements because their is no
web_seminars child element of the current context node. The first for-each
makes the context the web_seminars element. The second for-each is looking
for the web_seminars child of the web_seminars element. None exists, so
nothing is displayed.
3. You really should be using apply-templates instead of for-each. I have
included a sample transformation that uses both, to illustrate the
apply-templates approach.
<snip>
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list