RE: FOP : Grouping by position - Out Of Memory

I'm going to try to split up the making of the FO, 
and the rendering to PDF. 
I do not have the memory problem when i put 
1 record / page, but then there only half of the 
page is filled. And that's not the preferred layout.

-----Oorspronkelijk bericht-----
Van: David Carlisle [mailto:davidc@xxxxxxxxx]
Verzonden: donderdag 19 december 2002 11:08
Aan: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
Onderwerp: Re:  FOP : Grouping by position - Out Of Memory



> I've tried the following-sibling axis, but then i get errors from
> FOP.

FOP is an FO renderer, so it only processes an FO document.

It doesn't care how that FO was made. Even if the calling sequence is
automated so the transformation happens transparently, logically these
operations are quite distinct (and if you are getting short of memory
you may be better to keep them really distinct, and run the
transformation as a separate process, writing to a file that you then
give to FOP).

So you need to make sure whether it is FO or your XSLT engine (xalan,
probably) that's running out of memory. If it is FOP then changing the
XSLT to use some other grouping technique will not help at all as if you
generate the same FO document then FOP is going to run out of memory at
the same point, whether that document was created using keys or the
following-sibling-access or written by hand in notepad.

David

_____________________________________________________________________
This message has been checked for all known viruses by Star Internet
delivered through the MessageLabs Virus Scanning Service. For further
information visit http://www.star.net.uk/stats.asp or alternatively call
Star Internet for details on the Virus Scanning Service.

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


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