loc wrote:
> On Feb 21, 6:10 am, Martin Honnen <mahotr...@yahoo.de> wrote:

>> Then process each 'TransactionLine' element and output what you want to
>> output:
>>
>> <xsl:stylesheet
>>    xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
>>    version="1.0">
>>
>>    <xsl:strip-space elements="*"/>
>>    <xsl:output method="text"/>
>>
>>    <xsl:template match="/">
>>      <xsl:apply-templates
>> select="NAXML-POSJournal/JournalReport/SaleEvent/TransactionDetailGroup/TransactionLine"/>
>>    </xsl:template>
>>
>>    <xsl:template match="TransactionLine">
>>      <xsl:value-of
>> select="/NAXML-POSJournal/TransmissionHeader/StoreLocationID"/>
>>      <xsl:text>,</xsl:text>
>>      <xsl:value-of
>> select="/NAXML-POSJournal/JournalReport/SaleEvent/BusinessDate"/>
>>      <xsl:text>,</xsl:text>
>>      <xsl:value-of select="ItemLine/ItemCode/POSCodeFormat/@format"/>
>>      <xsl:text>,</xsl:text>
>>      <xsl:value-of select="ItemLine/ItemCode/POSCode"/>
>>      <xsl:text>&#xA;</xsl:text>
>>    </xsl:template>
>>
>> </xsl:stylesheet>

> Thanks, it works great, just what I wanted.  One question, I'm just
> trying to get a better understanding of how this works, why isn't a
> for-each needed even though there are multiple matches for
> <TransactionLine> and the data under it?

The apply-templates 
select="NAXML-POSJournal/JournalReport/SaleEvent/TransactionDetailGroup/TransactionLine" 
selects all 'TransactionLine' elements for processing, that is the 
reason you do not need a for-each.

-- 

	Martin Honnen
	http://msmvps.com/blogs/martin_honnen/