[XSL-LIST Mailing List Archive Home] [By Thread] [By Date]

RE: [xsl] Lookup efficiency in XALAN vs. Saxon

---

---

Jay,

Unfortunately I can't take you further on this since I've never run into the particular problem. It sounds at this point like a Xalan problem, or a problem with your installation (which might be easily fixed).

Xalan has a list; they could undoubtedly say better. (They will need to know more details of your installation.) This kind of thing isn't really uncommon, so an answer is probably known.

As for whether Saxon fares better: it's easy enough to try, and an excellent idea.

Good luck,
Wendell

ps, note that a bit from my post from yesterday doesn't make sense if you scrutinize it:

<xsl:for-each select="$keyfile">
   <xsl:when test="not(key('keys-by-id', $id))">...</xsl:when>
</xsl:for-each>

Of course the entire <xsl:choose> would have to be inside the for-each, and may have to be emended accordingly (since its context node is different from the main template's).

What Mike suggested, binding a flag to a variable, is a workaround for that.

Cheers, W

At 07:07 PM 11/20/2003, you wrote:

Wendell,
        thanks for the two ideas.... Unfortunately...

        using a variable, allow it to die much earlier (after 30 records)
with the same
        "(Location of error unknown)XSLT Error (java.lang.OutOfMemoryError):
null"

        and the second method (with xsl:key) died before processing any
records, again with the same
        "(Location of error unknown)XSLT Error (java.lang.OutOfMemoryError):
null"

        does Saxon or any other xslt processors deal with this simple table
lookup any better?

Jake

___&&__&_&___&_&__&&&__&_&__&__&&____&&_&___&__&_&&_____&__&__&&_____&_&&_
"Thus I make my own use of the telegraph, without consulting
the directors, like the sparrows, which I perceive use it
extensively for a perch." -- Thoreau


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

---