Description Yaytay 2011-10-27 17:38:29 EDT

Build Identifier: 20110916-0149

For a report to support any paging the layoutEngine.layout method must be called with the final parameter set to true.
The RunAndRenderTask has a completely different way to calculate this final parameter from RenderTask.
In RunAndRenderTask the default is for the parameter to be true, it has to explicitly turned off by options to go away.
In RenderTask the parameter is more complex and effectively cannot be set to true for a page-break-pagination emitter unless either the report only has one page (?) or htmlRenderOption.getHtmlPagination( ) is true - but if HtmlPagination is true the layout engine does paper-size-pagination (or at least, it splits large tables into multiple pages).

I think the correct fix is in RenderTask.render(), where PAGE_BREAK_PAGINATION.equals( pagination ) and !paged, the call to layout should permit paging (because the emitter wants to do it):
    layoutEngine.layout( executor, report, emitter, true );
This fix would tally with the PAPER_SIZE_PAGINATION.equals( pagination ) case.

Reproducible: Always

Steps to Reproduce:
1. Take an emitter that is set for page-break-pagination.
2. Output a report with page breaks using the report designer - the report will page correctly.
3. Output the same report using separate Run and Render tasks - the report will not page correctly.