JasperReportsIntegration provides an interface to use the JasperReports reporting engine in an Oracle database application, specifically with Oracle Application Express (Oracle APEX).
It would be helpful to ignore the pagination through the api. I have given it some thought:
Typically, you would want it dependent on the export type, i..e. PAGINATION for PDF, but NO PAGINATION for HTML and Excel. Nevertheless, there might be edge cases
You can set the parameter isIgnorePagination in the report file itself, but then it will also affect the PDF output of the report.
You cannot set it through the file jasperreports.propertiesspecifically for the html and xls export formats
The best way is to implement it through the API for the edge cases.
But I will also implement a parameter dynamicPagination in the application.properties file. In most cases, using the dynamic pagination (for excel and html but not pdf) is perfectly fine. No overhead needed for this simple use case.
Only if you should have these strange edge cases where you would want to have pagination in your excel and html exports, you could override the setting through the API.
As @ogrossmann writes here: https://github.com/daust/JasperReportsIntegration/issues/113
It would be helpful to ignore the pagination through the api. I have given it some thought:
isIgnorePaginationin the report file itself, but then it will also affect the PDF output of the report.jasperreports.propertiesspecifically for the html and xls export formatsThe best way is to implement it through the API for the edge cases. But I will also implement a parameter
dynamicPaginationin theapplication.propertiesfile. In most cases, using the dynamic pagination (for excel and html but not pdf) is perfectly fine. No overhead needed for this simple use case.Only if you should have these strange edge cases where you would want to have pagination in your excel and html exports, you could override the setting through the API.