RE: [xsl] Connecting the Source and Destination fields

Subject: RE: [xsl] Connecting the Source and Destination fields
From: "Yaswanth" <yaswanth.mtrx@xxxxxxxxx>
Date: Mon, 20 Aug 2007 16:32:29 +0530
I already told my requirement it done!
Only thing is I couldn't get is from where you are fetching StartEvent ..
>From this statement 
<xsl:variable name="startEvent" select="connection[not(@source =
../connection/@destination)]" as="element()"/>

Even that is clear!

Thanks 



-----Original Message-----
From: Andrew Welch [mailto:andrew.j.welch@xxxxxxxxx] 
Sent: Monday, August 20, 2007 4:17 PM
To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
Subject: Re: [xsl] Connecting the Source and Destination fields

On 8/20/07, Yaswanth <yaswanth.mtrx@xxxxxxxxx> wrote:
> In
> <xsl:apply-templates select="key('conn-by-source', $startEvent)"/>
>
> How will I know the start Event?
>
> Start Event (Source) has to be chosen in such a way that it is not present
> in the destination of any Connection! And then it has to proceed with the
> remaining things...
>
> Isn't it?

Are you asking me?  Surely you know the requirements?

Given what you've just said, you need to modify the solution I posted to be:

<xsl:variable name="startEvent" select="connection[not(@source =
../connection/@destination)]" as="element()"/>
<xsl:value-of select="$startEvent/@source"/>
<xsl:apply-templates select="key('conn-by-source', $startEvent/@source)"/>

If this doesn't do what you need, pleeeeease take the time work out
all of the requirements in the first place and not drip feed them one
by one... it's really frustrating from this side of the divide as its
gives the appearance the solution is incorrect when in fact the
requirements are underspecified.

Current Thread