What happens is that, if a development requirement is assigned to somebody;
it has its development jobs. But one person can have many development
requirements i.e. <developmentrequirement drid='1'> with it's DJ's i.e.
<developmentjob djdrid="1">, <developmentrequirement drid='2'> with it's
DJ's i.e. < developmentjob djdrid="2">, <developmentrequirement drid='3'>
with it's DJ's i.e. < developmentjob djdrid="3">

What I want to achieve is that once you choose the person with a DR let's
say <developmentrequirement drid='1'>, on the display I get:

<Developmentrequirement drid='1'> with it's <developmentjob djdrid='1''>,
then it gives me the rest of the DJ's

<Developmentjob djdrid='2''>, <developmentjob djdrid='3''> without there
DR's


-----Original Message-----
From: owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx
[mailto:owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx]On Behalf Of Bryan Rasmussen
Sent: 12 March 2002 12:52
To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
Subject: RE:  avoiding repetition - more refined


it's sometimes hard to understand what you're going for, I sympathise cause
I have the same problem,  let me see if I understand.
Inside of your DevelopmentRequirements element you have a with element that
has a string value, steve, and a sequence of DevelopmentJob elements with
different djid attributes.
the example you gave was
<DevelopmentRequirement drid="1">
....<with>steve</with>....</DevelopmentRequirement>
the drid attribute was incidental, that is to say you could have
<DevelopmentRequirement drid="7">
...<with>steve</with>...</DevelopmentRequirement> and want to match that.
It seems in that case that your best bet is to have a global parameter $name
that you check against DevelopmentRequirement,
like the following
<xsl:param name="name" select="'steve'"/>
<xsl:template match="calls">
<xsl:apply-templates select="DevelopmentRequirement[with = $name]"/>
</xsl:template>

then you'll have to send in the parameter name from you're application, I
suppose you're still using that hta you had way back when, so I know at any
rate that you have the code to do that part.


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list



 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list