Hi, I have refactored the ZKJRViewer class only replacing deprecated methods with new methods, is it wrong? In my conception the refactor is the next step, because it can cause a lot of refactors in other classes and at this moment I need a fast and good solution for an input of JasperPrint List for print many documents in one click.
In my changes to make it possible I have duplicated the constructor of ZKJRViewer by changing the input parameter for JasperPrint List and make several changes in class.
The patch is in attachment.
WDYT?

Regards.
Tiago Ceridorio

Committed solution from @Thomas Bayen in his ReportStarter:
https://bitbucket.org/tbayen_bxservice/de.bxservice.report.jasper/src/tip/de.bxservice.report/src/de/bxservice/report/ReportStarter.java

For the class ZkJRViewer - we have discussed with @Diego Ruiz and it seems the approach of that viewer is very wrong.

ZkJRViewer is not just a viewer class - but is creating the report (a model class), a better approach would be to refactor ZkJRViewer to call the ReportStarter - and make viewer just that -> a viewer of files rendered in another class.
This is inline with https://idempiere.atlassian.net/browse/IDEMPIERE-2684#icft=IDEMPIERE-2684 and allowing jasper to be a replaceable plugin as @Thomas Bayen has proposed and is trying with his de.bxservice.report.jasper plugin (but ZkJRViewer is making it difficult).

WDYT?

Regards,

Carlos Ruiz