If this helps anyone out... When I try it with a smaller xml file, it will
work fine.. If I have only around 150 commission nodes it will work rather
quickly.. but the complete xml file has over 2000 commission nodes.. and
that is where it hangs up.

----- Original Message ----- 
From: "Corey Wilson" <corey@xxxxxxxxxxxxxxxxxxxxxx>
To: <XSL-List@xxxxxxxxxxxxxxxxxxxxxx>
Sent: Monday, June 09, 2003 16:22
Subject:  unefficiate xpaths


> I am not sure how much help anyone can give me on this, but any help would
> be very much appreciated.  I have a rather large (1.5 meg) xml file and it
> is taking about 11 mins to evaluate this xsl:for-each statement... I
haven't
> been using xsl for long, so I may be going about it completely wrong
>
> <xsl:for-each
select="//clients/client[count(commissions/commission[earnerId
> = //earners/earner[type = $rptType]/id]) = 0 and <website=$prodClass)]">
>
> $rptType and $prodClass are both global variables
>
> I know this doesn't tell you much about how much processing is going on...
> but there has to be a more efficient way of getting the nodes I want than
> the 11 min. example I have above...
>
>
>  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
>


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