Hi: I have a question related to performance issues. How large an xsl-fo file can be? How large volume it can support?
I have an application that fetched approx. 60,000 records fetched from database an populates in a fo:table-cell as text. Basically, it uses the following block of fo-tags repeatedly to populate a huge chunk of data. ------ <fo:table-row height="42pt" > <fo:table-cell > <fo:block><fo:block text-align="left"> <fo:inline ...> Some data </fo:inline> </fo:block> </fo:table-cell> </fo:table-row> ------ My specific questions are: - Can you suggest a shortcut so that fo-tags can pull data from the database directly? - What is the best suggested approach to handle large volume of data passed embedded inside fo-tags? We can think of the following: - Have a streaming fo input to the FOP renderer to generate PDF. Can you provide a sample code to handle FOP rendering to PDF from a FO file through streaming? - We were reading a link in FOP documents, it says "To minimize the amount of memory used by FOP, we wish to recycle FO Tree memory as much as possible. There are at least three possible places that FO Tree fragments could be passed to the Layout process, so that their memory can be reused: fo:block , fo:root and fo:page-sequence Could you please clarify with some supporting examples or some link that we can read to get the guideline? My last question: Is FOP designed to handle large volumes like this? Please reply soon. We are standing of major decision based on your answer. Thanks in advance, Regards, Debasish Jana --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
