Actually, for me, that's even another reason for using XSLT. But in the end, you have to live with your solution.
On 11.09.2008 17:45:05 Venkatesan, Balaji wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > Thanks. > > But the pdf document we create is NOT of the same style everytime, we > are creating documents of different look and feel (but all are pdf) > depending on the document name for a participant. Actually, I missed out > our data style. It should be: > > Participant1 DocumentA Client1 Plan11 > Participant2 DocumentB Client1 Plan11 > Participant3 DocumentC Client2 Plan21 > Participant4 DocumentA Client2 Plan21 > ..... > .... and so on. Eventhough Participant1 and 4 are using the same document > name, since they are under different client, their document definition > may be entirely/slightly different. > > I don't think we can have one common StyleSheet to print pdf for all > types of documents and that is why I am directly creating XSL-FO. > > Thanks > balaji > > =================================== > Balaji Venkatesan > *617-376-9257 > [EMAIL PROTECTED] > ING. Your future. Made easier.SM > =================================== > > - -----Original Message----- > From: Jeremias Maerki [mailto:[EMAIL PROTECTED] > Sent: Thursday, September 11, 2008 11:34 AM > To: [email protected] > Subject: Re: Need help in writing pdf with more than 1000 pages using > fop.. > > Please take a look at the embedding examples: > http://xmlgraphics.apache.org/fop/0.95/embedding.html#examples > > They give you hints on how to implement the process in the most > efficient way. > > It's bad practice to generate XSL-FO directly in code. It's messy and > hard to maintain. If you just send the participant data to a SAX stream > (define your own basic XML format with just the participant data, no > layout), you can separate out the layout logic into an XSLT stylesheet > that will take your XML format and turn it into XSL-FO. That keeps your > Java code clean and allows you to more quickly change layout stuff if > you need to. It also has the added benefit that you can do something > else with the XML data. For example, another XSLT stylesheet could turn > your participant data into HTML. The generation of the participant data > is practically equivalent to the ExampleObj2XML on the page indicated > above. > > If you stay on the SAX level, you can avoid building up the full > participant document in memory. FOP will rather process the content as > it comes in as individual calls to the SAX ContentHandler. > > If you can put each participant in a separate page-sequence you'll allow > FOP to run at very little memory usage. You can basically generate an > unlimited number of pages that way. Each participant is automatically > "flushed" to the PDF file that way. > > I hope that helps. > > On 11.09.2008 17:13:32 Venkatesan, Balaji wrote: > > > Hi, > > I have just started using FOP. I have a requirement to write a pdf > > file with more than 1000 pages.How can I do that? I am directly > > creating a XSL-FO string to create a pdf document and concatenating > > that into a big string, I know it wrong, Is there any other way?. > > Basically, we generate documents for multiple participants at the same > > > time and write all their data into a single pdf file. Here is an > example: > > > > > The data comes in this order : participant1, participant2, > > > participant3, participant4, participant5 ..... Participant1000 > > > > > > As soon as I am done with the first participant, I have to write his > > > > data into a pdf file and process the second participant and write > > > his data to the same pdf file and so on. > > > > > > How do I do this more effectively??? > > > > > > Advanced thanks for your help. > > > > > > -B > > > > > Jeremias Maerki > > > - --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -----BEGIN PGP SIGNATURE----- > Version: PGP Universal 2.8.3 > Charset: us-ascii > > wsBVAwUBSMk9AVIHx0ARICbPAQjwRQf/cEEvNSQip5nDGEIc2H0oUZA1Qg+ZT/wm > 110OwDJIY3zpi8b4BK3V/4HSC8+wFxiPPaXEnVevpOUM65hR6826fpRRuHGP7j0f > CQVdWH4yfwTrLkMabu4jtQCOybLHhEUo+uU5kYg4OZWbDKuw4t14gamo7FrJ1jft > gdUaDGmIKauf68XXnSW/GtUNcZaxHsT35Cq09+aVxBosbdoeCuDmk0HSvyqdUfEE > ljx+gPCzxt6Sxdg3izsj4baQCDH3iR7m9PXrzgP5QFwY1myZO+9XPKij+I/0UQKT > 9T/HLtphntXmTQ/Qi5TQRm2/H+XC24h3k5s0Om//ZfmwcNMkut4M7g== > =BvnA > -----END PGP SIGNATURE----- > > --------------------------------------------------------- > > NOTICE: The information contained in this electronic mail message is > confidential and intended only for certain recipients. If you are not an > intended recipient, you are hereby notified that any disclosure, > reproduction, distribution or other use of this communication and any > attachments is strictly prohibited. If you have received this communication > in error, please notify the sender by reply transmission and delete the > message without copying or disclosing it. > > ============================================================================================ > Jeremias Maerki --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
