neil cave wrote:
<xsl:template match = "ACCOUNT-LIST">
<xsl:if test="string-length(ACCOUNT-NO/text() > 0)">
<xsl:element name = "ACCOUNT-LIST">
<xsl:for-each select="."/>
</xsl:element>
</xsl:if>
</xsl:template>
and this writes a whole bunch of empty <ACCOUNT-LIST> elements
Which I guess is happening because somehow I'm not refering to the
correct occurence of the ACCOUNT-NO child node I'm dealing with? And
I'll need some xsl:for-each logic
Could you please provide a minimal example of an input tree that
reproduce the problem with that template rule?
Regards,
--drkm
___________________________________________________________________________
Yahoo! Mail réinvente le mail ! Découvrez le nouveau Yahoo! Mail et son
interface révolutionnaire.
http://fr.mail.yahoo.com
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--