Package org.pentaho.reporting.engine.classic.core.modules.output.table.base

Common base classes for the table style output targets.


Interface Summary

Class Summary
AbstractTableOutputProcessor The Table-Output processor uses the pagination stage to build a list of table-layouts.
ContentMarker Creation-Date: 04.10.2007, 14:54:24
DefaultTextExtractor Creation-Date: 02.11.2007, 14:14:23
FinishedMarker Creation-Date: 04.10.2007, 14:54:24
FlowReportProcessor Creation-Date: 03.05.2007, 10:30:45
SheetLayout The sheet layout is used to build the background map and to collect the x- and y-cell-borders.
SheetLayoutCollection Deprecated. no longer used.
SheetLayoutTableCellDefinition Todo: Document me!

Date: 31.03.2010 Time: 16:34:01

StreamReportProcessor Creation-Date: 03.05.2007, 10:30:02
TableBaseModule The module definition for the table export modules.
TableContentProducer After the pagination was able to deriveForAdvance the table-structure (all column and row-breaks are now known), this second step flattens the layout-tree into a two-dimensional table structure.
TableCutList Creation-Date: 26.08.2007, 15:06:45
TableLayoutProducer Creation-Date: 02.05.2007, 18:31:37
TableRectangle The TableRectangle contains GridCoordinates for the tables.

Package org.pentaho.reporting.engine.classic.core.modules.output.table.base Description

Common base classes for the table style output targets.


The TableExports add several restrictions to the report layouts.

Report elements must not overlay each other. It is ok for bands, but the actual data must never overlap. Once a cell is occupied, it cannot be redefined to contain data from other elements. CellData cannot be combined.

Backgrounds can only be defined for the complete cell.

How does the table export work?

All table targets use a two step process to create the output. In the first step, the layout is computed and styles information is collected. The style information will later be reused to form cascading stylesheets or to fill the Excel style tables.

Cell backgrounds are computed during the pagination phase and are stored in the SheetLayout; The content itself is only stored during the content-generation phase and is held in the TableContentProducer. Once the page is completed the computed content and the sheet-layout instace are forwarded to the Output-processor implementations.