Chris,
At 04:24 PM 4/1/2005, you wrote:
I have no way now to get the dates in order without calling some ridiculous
recursive template that sorts the nodes for me and prints the appropriate
one. Loop.. Print. which could result in a high number of passes..
Why not sort them with the same instruction you'd use to sort them if
converting them to an intermediate format?
<xsl:template match="/">
<table>
<xsl:apply-templates select="//Disbs | //Refunds">
<xsl:sort select="DisbDetail/Ddate | RefDetail/Rdate"/>
</xsl:apply-templates>
</table>
</xsl:template>
<xsl:template match="Disbs | Refund">
<tr class="{local-name()}">
... etc ...
</tr>
</xsl:template>
... the 'class' attribute there gets the value "Disbs" or "Refund" -- i.e.
the name of the matched element.
There are cases where complex sorting and grouping requirements push us
into having to process temporary trees, but I haven't yet seen anything
here that makes me think this is one of them.
Cheers,
Wendell
======================================================================
Wendell Piez
mailto:wapiez(_at_)mulberrytech(_dot_)com
Mulberry Technologies, Inc. http://www.mulberrytech.com
17 West Jefferson Street Direct Phone: 301/315-9635
Suite 207 Phone: 301/315-9631
Rockville, MD 20850 Fax: 301/315-8285
----------------------------------------------------------------------
Mulberry Technologies: A Consultancy Specializing in SGML and XML
======================================================================
--~------------------------------------------------------------------
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>
--~--