![](http://content.invisioncic.com/i328763/set_resources_3/84c1e40ea0e759e3f1505eb1788ddf3c_pattern.png)
ma_il
-
Posts
7 -
Joined
-
Last visited
Content Type
Forum
Downloads
Featured Visualizations
Knowledge Base
Documentation (PDF Downloads)
Blog
Documentation (Test Area)
Documentation
Dr. Jaspersoft Webinar Series
Security Advisories
Events
Profiles
Posts posted by ma_il
-
-
Managed to get it working after all.
What I finally did was:
- provide a copy of the datasource via a parameter in the parent report instead of trying to use the same datasource
- check "Title on a new page" in the subreport
Keeping the growing subreport in the Summary band of the parent wasn't problematic after all.
-
In theory, PDF/A-1 should be a subset of PDF/A-3 and thus work as well. Did you make any progress on the ZUGFeRD integration?
-
Hi all,
I'm trying to show a subreport at the end of my report which should
- start a new page
- grow to use as much space as it requires
- use the same datasource as the parent report
But so far I have been unable to get it to show up.
I have tried putting the subreport into the Summary section as well as the Last Page Footer. Also I have tried using the connection or the datasource from the parent report. I have tried toggling "Run To Bottom" and played around with the "Stretch Type" of the subreport element - all to no avail.
What _did_ turn out to be a good idea was to compile the subreport into a JasperReport object and set it as a report parameter to avoid classpath problems. So I'm sure that the subreport is valid and can be evaluated on its own.
If I can't get it to work I'm prepared to render the reports separately, export them to PDF and concatenate them via iText but first I'd like to try getting it to work "the right way".
-
Good point! Looks like it's only available via manual download?
JasperReports 6.0 licensing and iText 5.5
in Products
Posted
I just looked at the new JasperReports 6.0 version and realized that while 5.6.1 still used the LGPL-compatible version 2.1.7 of iText, the new 6.0 release depends on iText 5.5.0 which is licensed under AGPL instead.
Assuming that this doesn't break licensing per se (IANAL, I'm guessing you checked), this afaik still implies that users of JasperReports 6.0 will need to purchase an iText license if they want to use JasperReports in any product (even server-side-only). Is this intended? I just wonder because the issues has been discussed for older releases but I couldn't find any mention regarding this change.