Basically, this means that you have to try to design your stylesheet in a way, that you can produce multiple page-sequences (ATM, your stylesheet produces one single page-sequence). The reason for that: FOP can release memory after a page-sequence is processed, especially if there are no forward references. So if you can find logical points in your report where you can force a new page, you can start a new page-sequence. Sometimes it means that you have to do some crude line counting to guess at FOP's line break decisions, sometimes this is not necessary which makes the whole job easier.
HTH On 29.03.2006 21:52:28 njain wrote: > Page-Sequence optimization! Well I am not really sure how to do that. I > have tried to reduce the number of tables and font specifications in > table-cells. But if you could throw a pointer as to how I can achieve the > page-sequence optimization, that'd be really helpful. > I have pasted the xsl file here. (It's big one though). Let me know if you > can deduce something from this which could help me in doing the > optimization. Jeremias Maerki --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
