XSLT loop.

[Iain]

Hi all,

I am try to split the some data out of a nested xml file and get all the
data in one new xml file. I have two XSLT files one takes the personal
information and one takes the data out of the fund section , then I import
each xml files into the datebase and do I relationship between the two.
This is not what my boss wants as he wants one xml file

This is my current XML

<message>
<personal>
<forenames>John </forenames>
<surname>Smit h</surname>
<policynumber>1 23456</policynumber>
<person>
<policydetail s>
<fund>
<code>ABC</code>
<units>123</units>
</fund>
<fund>
<code>xyz</code>
<units>987</units>
</fund>
</policydetails>
</message>

and I am trying to acheive this

<message>
<personal>
<forenames>John </forenames>
<surname>Smit h</surname>
<policynumber>1 23456</policynumber>
<person>
<policydetail s>
<fund>
<code>ABC</code>
<units>123</units>
</fund>
</policydetails>
<personal>
<forenames>John </forenames>
<surname>Smit h</surname>
<policynumber>1 23456</policynumber>
<person>
<policydetail s>
<fund>
<code>xyz</code>
<units>987</units>
</fund>
</policydetails>
</message>

I have been trying with <xsl:for-each> looping through personal and
policydetails but am getting some strange results!! Can somebody please
point me in the right direction.

TIA

[Joe Kesselman]

It's hard to offer advice without knowing details of what your
stylesheet looks like. Can you come up with a minimal example that
demonstrates the problem?
--
() ASCII Ribbon Campaign | Joe Kesselman
/\ Stamp out HTML e-mail! | System architexture and kinetic poetry

[Iain]

Here is the stylesheet.

<xsl:for-each select="message/fund">

<xsl:for-each select="message ">

<xsl:element name="details">
<xsl:element name="forenames "><xsl:valu e-of
select="//forenames"></xsl:value-of>
<xsl:element name="forenames "><xsl:valu e-of
select="//surnames"></xsl:value-of>
<xsl:element name="forenames "><xsl:valu e-of
select="//policynumber"></xsl:value-of>

<xsl:element name="forenames "><xsl:valu e-of
select="//fund"></xsl:value-of>
<xsl:element name="forenames "><xsl:valu e-of
select="//code"></xsl:value-of>
<xsl:element name="forenames "><xsl:valu e-of
select="//units"></xsl:value-of>
</xsl:element>

</xsl:for-each>

</xsl:for-each>

"Joe Kesselman" <ke************ @comcast.net> wrote in message
news:n9******** *************** *******@comcast .com...

It's hard to offer advice without knowing details of what your stylesheet
looks like. Can you come up with a minimal example that demonstrates the
problem?

[Andy Dingley]

Iain wrote:

I have been trying with <xsl:for-each> looping through personal and
policydetails but am getting some strange results!! Can somebody please
point me in the right direction.

<xsl:template match="message" >
<xsl:copy>
<xsl:for-each select="policyd etails/fund" >

<xsl:copy-of select="../preceding-sibling::person al [1]" />

<policydetail s>
<xsl:copy-of select="." />
</policydetails>
</xsl:for-each>
</xsl:copy>
</xsl:template>
This is two loops, one (implicit) for <message> and an explicit one for
<fnud>
We don't try to "synchronis e" loops for people and funds, that never
works in XSLT. Instead we loop over whatever has the ordinal
relationship, then extract the dependent part (the <personal> with a
lookup).

There's also a typo in your XML <personal> / <person> and I don't like
its structure anyway. If <message> ever contains multiple <personal>s,
then you're relying on the _ordering_ of XML, not the nesting.
Personally this always makes me nervous.

[Iain]

<di*****@codesm iths.com> wrote in message
news:11******** ************@v4 6g2000cwv.googl egroups.com...

Iain wrote:

I have been trying with <xsl:for-each> looping through personal and
policydetails but am getting some strange results!! Can somebody please
point me in the right direction.
<xsl:template match="message" >
<xsl:copy>
<xsl:for-each select="policyd etails/fund" >

<xsl:copy-of select="../preceding-sibling::person al [1]" />

<policydetail s>
<xsl:copy-of select="." />
</policydetails>
</xsl:for-each>
</xsl:copy>
</xsl:template>
This is two loops, one (implicit) for <message> and an explicit one for
<fnud>
We don't try to "synchronis e" loops for people and funds, that never
works in XSLT. Instead we loop over whatever has the ordinal
relationship, then extract the dependent part (the <personal> with a
lookup).

There's also a typo in your XML <personal> / <person> and I don't like
its structure anyway. If <message> ever contains multiple <personal>s,
then you're relying on the _ordering_ of XML, not the nesting.
Personally this always makes me nervous.

Many thanks. This worked a treat.

If <message> ever contains multiple <personal>s,
then you're relying on the _ordering_ of XML, not the nesting.
Personally this always makes me nervous.

I agree and understand. However I am limited to how the XML is structured
by the Filemaker database I need to import the data into.