Category: | Bug report |
Priority: | Immediate |
Status: | Resolved |
Project: | Severity: | Critical |
Resolution: | Fixed |
|
Component: | Reproducibility: | Always |
Assigned to: |
The report engine renders the wrong information after a page break. More precisely when two lists are used next to each other and each list triggers a page break, the engines uses the wrong list data after the page break.
The information of the lists get mixed up causing 3 severe problems:
1/ information to be rendered in the wrong place,
2/ wrong information to be renderend,
3/ information loss because information of the other list is used
Report 'XMLDemo1a - fetching using absolute paths.jrxml' has been created as a reference report to show the correct rendering. On page 3 of 'XMLDemo1a - fetching using absolute paths.pdf' the correct and expected information is displayed. Also the left and right list is clearly marked. The page break occurs between page 2 and page 3.
To illustrate this problem we've created a report called 'XMLDemo1b - fetching using relative paths - wrong information.jrxml'. After the page break the left list contains information that belongs to the right list. On page 3 of 'XMLDemo1a - fetching using absolute paths.pdf'.
The data adaptor we used to illustrate the problem is the default xml data adaptor provided by the library. We include the adaptor (XMLDataAdaptor.xml) and the xml data (xmldata.xml) that has been used to render the reports.
I've uploaded all files in a zip file called (archive.zip). Alternatively you can download the files using this link https://cl.ly/0F3b1Y0X381Y .
Please contact me if you have questions or if you need more information.
Thomas
7 Comments:
Fixed at https://github.com/Jaspersoft/jasperreports/commit/918b2d402b5650d152c6d...
The problem was that $P{REPORT_DATA_SOURCE} (and other parameter values) was mixed up between several lists that used the same subdataset.
Regards,
Lucian
Dear Lucian
Thank you for investigating and fixing our bugreport so swiftly. When will this fix be release. I'm sure you'll understand that we are anxious to deploy your fix in our software.
Thomas
The latest jar published at http://jaspersoft.jfrog.io/jaspersoft/jr-ce-snapshots/net/sf/jasperrepor... contains the fix.
You can also consider fetching the sources for the JR version that you are currently using, patching it with the fix mentioned above and building a patched JR jar.
Regards,
Lucian
Dear Lucian
I used the 6.4.1 snapshot jar and I can hereby confirm that the bug is fixed.
Thanks
Thomas
We are using jasper 6.4.1 in production and we noticed that this bug has not been fixed. Regression? Or did the fixes not reached version 6.4.1 ?
The fix was not included in JasperReports 6.4.1, but is part of 6.4.3.
Please reopen if the problem is still present in 6.4.3.
Regards,
Lucian