DisplayTag

Too memory used in pdf export of large table

Details

  • Type: Improvement Improvement
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: 1.0
  • Fix Version/s: None
  • Component/s: Export
  • Labels:
    None

Description

When large table are exported as PDF the default class do not use fragmented table pattern of the itest package, so for large table there is a large amount of memory used. Problem can solved by adopting the fragmented table technique.
Fix available but only for rel 1.0.

Activity

Hide
Jorge L. Barroso added a comment -
Emilio, could you attach the patch for 1.0? I'd like to take a look to consider applying it to 1.1, as I'm working on changes to the 1.1 exports. Thx.
Show
Jorge L. Barroso added a comment - Emilio, could you attach the patch for 1.0? I'd like to take a look to consider applying it to 1.1, as I'm working on changes to the 1.1 exports. Thx.
Hide
Emilio Dolce added a comment -
remember that in order to use this patch you must use iText rel. 1.4
Show
Emilio Dolce added a comment - remember that in order to use this patch you must use iText rel. 1.4
Hide
Dan Epstein added a comment -
Are there any plans to use the iText PdfPTable and the fragmented table method for 1.1?
(http://itext.ugent.be/library/com/lowagie/examples/objects/tables/pdfptable/FragmentTable.java)
I am also having problems with running out of memory exporting large tables. It would require several changes to the export view, table writer, and table decorators.
Show
Dan Epstein added a comment - Are there any plans to use the iText PdfPTable and the fragmented table method for 1.1? (http://itext.ugent.be/library/com/lowagie/examples/objects/tables/pdfptable/FragmentTable.java) I am also having problems with running out of memory exporting large tables. It would require several changes to the export view, table writer, and table decorators.

People

Vote (1)
Watch (2)

Dates

  • Created:
    Updated: