> If you don't use iText correctly, you can also easily have memory > issues; I don't know about BFO, but iText was designed for web > appplications. As soon as a page is finished, we try sending the > complete page to the OutputStream so that it's not kept in memory. > >> Kindly suggest the right way to produce such a huge PDF dynamically >> using iText in the web. > > That question is too broad to explain in a mail; but there's a book > about iText... > --
If you don't want to read the documentation or source code, you can at least empirically determine where any problems are by doing a heap or memory dump after each page and see if you are accumulating junk, http://java.sun.com/javase/6/docs/technotes/tools/share/jhat.html or if worried about speed, http://java.sun.com/developer/technicalArticles/Programming/HPROF.html I think in the past someone pointed to PDFTEmplate.release(). If you grep the source code for something like "public.*release" you can get a good idea of which objects may need to be explicitly released. If you want to quickly create a large document that loads and views on a user machine while consuming few resources, I'm not sure there is much PDF help for that but I would suggest pdftotext [ LOL but serious suggestion ]. _________________________________________________________________ Rediscover Hotmail®: Get quick friend updates right in your inbox. http://windowslive.com/RediscoverHotmail?ocid=TXT_TAGLM_WL_HM_Rediscover_Updates1_042009 ------------------------------------------------------------------------------ This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com _______________________________________________ iText-questions mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/itext-questions Buy the iText book: http://www.1t3xt.com/docs/book.php
