"Edward L. Knoll" wrote:
I have a set of style sheets which have a sever performance problem.
Distilled (hopefully not diluted past usefulness), I am processing a
large set of sibling elements a few elements at a time. I believe the
problem is with the following statement (which I've changed/condensed
the expression of):
<xsl:for-each select="/elements[ (position() >= $Start) and
(position() <= $End) ]">
...
</xsl:for-each>
I was referred to a FAQ on grouping and this led me to attempt to setup
some kind of solution utilizing keys. Unfortunately, the XSL reference
I have has no information on <xsl:key> and my favorite FAQ has a list of
topics under keys with no corresponding content. Anyway, my
XSL processor (Xalan) doesn't like my key definition. Is the
"use" parameter limited from being a numerical expressions?
<xsl:key name="PageKey" match="/gnsl:Results/gnsl:Table/gnsl:Row"
use="((position() - 1) / $RowsPerPage) + 1)" />
Sorry, saw part of the problem as soon as a hit send: ' / ' instead of '
div '. I've been working across too many different contexts and need
compilers to tell me when I'm mixing language syntax.
Now it's taking my key definition, but when I try to reference the key
to get the associated elements, I seem to be coming up with an empty
list. I'll keep pluggin and see if I can figure it out.
Ed Knoll
--
Edward L. Knoll Phone (work) : (719)484-2717
e-mail (work) :
ed(_dot_)knoll(_at_)cosd(_dot_)fedex(_dot_)com
e-mail (business): eknoll(_at_)sf-inc(_dot_)com
e-mail (personal): edward(_at_)elknoll(_dot_)com
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list