I suggest going with #1. Build all your static content in advance, and
only render/insert the pages with dynamic content as needed.
--Mark Storer
Senior Software Engineer
Cardiff.com
import legalese.Disclaimer;
Disclaimer<Cardiff> DisCard = null;
________________________________
From: Herold, Douglas [mailto:dher...@kheaa.com]
Sent: Thursday, September 22, 2011 7:32 AM
To: 'itext-questions@lists.sourceforge.net'
Subject: [iText-questions] [Book]
Hi
We are going to create a large report (30 or 40 pages) for our
company using iText for Java. The report will have a lot of static data
and images. The report will also have dynamic data and graphs about the
current logged in user. I was wondering what the best way to handle the
static data and images would be. I have looked all over the internet and
cannot find any articles on this subject. I have also asked the question
in a few forums with no real help. These reports will need to be
generated on the fly and returned to the user immediately, so
performance is a must. The report will be served up using a Java
Servlet in a web application.
These are some of my initial thoughts on how to solve the
problem. I would really like some input on what issues other people
have had when doing a report like this so I can write/design a good
solid report that is easily maintained.
1.) We could create a PDF with all the static content and
images. Then open the PDF with Java and insert the dynamic content and
graphs. Is there a way to put place holders in the PDF that I could use
with the Java to insert the dynamic data and graphs (which would be
images).
2.) Place the static data in a database and retrieve it
whenever a report is generated. To me the database design would be
complex. It would have to take into account pages, paragraphs, titles.
It would also have to takes into account images and the placement of the
image on the page.
3.) We could put the static content in an XML file and cache
the content in the Servlet Context when it initializes. This might help
with performance issues. I would think we would still have the same
design issues as the database would have, but might be easier to
maintain.
I am using the iText book as a reference, but did not see that
it covered this particular issue.
Thanks For Your Time
Doug
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________
iText-questions mailing list
iText-questions@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/itext-questions
iText(R) is a registered trademark of 1T3XT BVBA.
Many questions posted to this list can (and will) be answered with a reference
to the iText book: http://www.itextpdf.com/book/
Please check the keywords list before you ask for examples:
http://itextpdf.com/themes/keywords.php
