Date: Fri, 16 Jan 2009 09:01:31 -0000
Subject: Re: [saxon] Saxon B
To: "'Mailing list for the SAXON XSLT and XQuery
I've never been successful trying to
allocate more stack space to the Java
VM. The amount of heap space will
make no difference to this error.
The most likely explanation for the
different behaviour is simply that your
application code is using some of
the stack space that would otherwise be
available to Saxon.
can't really offer any other suggestions without seeing your code.
deeply nested do you think its calls are?
(By the way, it's helpful
if you can choose a subject line that describes
the problem. If everyone
titled their posts as you have done, it would
become very difficult to
find your way through the archives or through
16 Jan 2009 07:58:37 +0100
From: "Roberto Cisternino" <email@example.com
Subject: [saxon] Saxon
Content-Type: text/plain; charset="utf-8"
need help to understand why Saxon B 220.127.116.11 is behaving
depending if I use it from the command line or direclty from
a java program.
Using the command-line the stylesheet works perfectly
and the transformation
generates as expected a good result.
Saxon from a Java program and the same stylesheet caused the
javax.xml.transform.TransformerException: Too many
calls. The stylesheet may be looping.; SystemID:
For sure the source XML and the stylesheet are enought complex,
but I am
surprised I cannot obtain the same result using one of the two
I tuned the VM to provide more heap memory or
stack, but the result was
always the above error.
appears too early in the transformation, and this surprise me more
more as the transformation is enough long (less than half a minute)
What are the default memory settings for the Saxon
B command-line ?
Any ideas ?
I will appreciate very much any
Thank you in advance
-------------- next part --------------
An HTML attachment