Hello John,
assuming all inputs are descendants of one single
<HSDataContainerType list="true" name="Inputs" ...> and the same for
outputs, consider using three templates instead of one:
<xsl:template match="HSDataContainerType[contains(@name, 'Inputs']">
<!-- HTML output for "Inputs" heading comes here -->
</xsl:template>
<xsl:template match="HSDataContainerType[contains(@name, 'Outputs']">
<!-- HTML output for "Outputs" heading comes here -->
</xsl:template>
<xsl:template match="HSDataContainerType">
<!-- HTML output for fields that are not headings comes here -->
</xsl:template>
Regards,
Markus
__________________________
Markus Abt
Comet Computer GmbH
http://www.comet.de
----------
Von: John Liebermann
Gesendet: Samstag, 16. August 2003 00:52
An: xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
Betreff: RE: [xsl] <xsl:for-each> not working...
[...]
I was using a for-each loop with ancestor::* to clearly display the path to
each field. That works perfect. The problem is that i don't process Inputs
and Outputs separetely. They are both of <HSDataContainer> type so i use :
--------------------------------------------
<xsl:template match="HSDataContainerType">
<xsl:choose>
<xsl:when test="contains(@name, 'Inputs')">
<img src="dcopenicon.gif">
<a href="#in"><b><xsl:value-of select="@name"/></b></a></img>
<div style="margin-left: 3em;">
<xsl:apply-templates select="*"/></div>
</xsl:when>
. exactly the same for 'Outputs'
--------------------------------------------
[...]
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list