This works fine here with 8.4
At 19:40 2005-06-14, you wrote:
I have seen this error with
Saxon8.2 but it is not a problem with Saxon7.8. My doc is about 30Kb that
recurses about 115 times. This all runs fine in 100Mb of memory space on
I agree with you in that certain Saxon behavior introduced recently has
threatened my existence. My entire product and company is based on the
Saxon transform engine. I believe that XSL is *the way* to produce
complex web applications. I have no choice but to continue using Saxon7.8
and carefully lift code from later versions to fix bugs.
I agree that Saxon is at the sole discretion of Mike Kay. I'm sure he
understands that there is a vast installed base that depends on backward
compatibility. In retrospect, backward compatibility is one of the
toughest things that MS, for instance, has to deal with. I respect Mike
Kay and anyone that has to balance that with the fruits of
Alan Painter wrote:
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
I've been using Template recursion in order to iterate over the N
of a node in a big input document, each node creating a separate
Haven't had any problem to date, even with big files (100Mo) and around
100 output documents.
But I just ran into a case of "StackOverflowError":
SXLM0001: Too many nested apply-templates calls. The stylesheet is
Sure, it's looping, but over the nodes that I need to output, not in
So I thought that I'd try the Saxon extensions that allow iteration, to
wit the "saxon:while"
extension and the "saxon:assignable" attribute to xsl:variable,
along with "saxon:assign".
I noticed that the 8.4 documentation says that "saxon:assign"
may go away in the future.
However, in spite of repeated attempts and tweaks, I couldn't get
saxon:assign to work:
my global variable remained a constant value:
select="0" saxon:assignable="yes" />
<saxon:while test="$topCurTradePart lt
Note: I tried both the "select" and "expr" attributes
So I'm in a corner and I'm curious what I should do:
-- Try to pursue the "saxon:assign" workaround, in the hopes of
making it work
-- Modify a configuration (which?) in order to keep from having
StackOverFlow exception in a normal recursion.
Thanks for pointers.
_______________________________________________ saxon-help mailing list