We want to generate Reports either embedded as html pages in a web app or downloadable as a pdf. Hence I came across Jasper Reports because it thought it would fullfill these requirements.
Currently we assume our report will have about 50-100 pages, consisting of nearly only histograms and some tables. The data is retrieved by some expensive queries from our DB.
After evaluating it the whole day i have several doubts regarding web app aspects.
1) Pagination: Of course i don't want to display all pages in a single web page. we need something like pagination. but Jasper Reports seems not to support this approach. The wepp demo, which comes with Jasper Reports, sketches the way to go: I have to create a JasperPrint, which is already the full report, allocating unrequired memory and which has performed the expensive queries. Then I could display a single page. But doing this again and again for each page does not appear as a proper solution to me.
2) As mentioned above, our report will mostly consist of diagrams. Images are generated during Exporting the JasperPrint to its output format. If I understand everything correct, the ImageServlet, which comes with Jasper, is capable but retrieve these images bei i) Reading the generated images from the file system ii) the exporter has stored them in the session (therefore in memory).
Since I think we will have a lot of images ii) is not an option, if we want to keep the memory footprint of the webapp low. But on the other hand flooding the file system with files is also not the best idea i could imagine. Does it delete the files somewhen?
Did I got something wrong? Is my understanding Correct?
Thanks, Lars