we ran into a similar problem a
couple of weeks ago. The most suitable solution that was offered then by our
colleagues in the list was to portion the transformation process. FOP seems to hold its breath until
it dives out of the waters of transformation at the other end of its page
In our case, it wasn't mass
data but an editorial document with lots of graphics, in reference to which I
was advised to use headers (of a certain level) to start a new page master
I think, some way or the other
you could find a similar solution.
Dott. Matthias Fischer
Fax (08241) 9686-26
e-mail: [EMAIL PROTECTED]
I am attempting to do database publishing using
fop to format the output. I have created a style sheet that creates a table of
contents and an index for my document using <fo:basic-link
internal-destination=...> in combination with id attributes. A larger
document is represented by an XML file of approximately 8MB and contains
thousands of such links. I am finding that the JVM memory pool required to
process this is about 750MB at this point. My database is not yet complete and
the documents are likely to grow both in size and number of links a good bit
before I am done.
I have tried running this on a machine with 512MB
of memory and it trashed hopelessly for 12 hours without completing. I have 1
machine with 1GB of RAM that I normally reserve as a server that can do the
processing in 1/2 an hour, but I am worried that I will lose the ability to
create the document as it continues to grow.
Do you have any suggestions that would help tame
the memory utilization? Will the next release of fop be able to process
links with a smaller amount of memory?