chamberlain

Problem solved! I recompiled my reports and the problem is now gone, so I can use the standard JR 3.7.3 release without changing anything. Thank you for the tip!

Thanks for your quick fix Lucian! In the meantime, I will try recompiling our reports with the latest JR version. Luckily, iReport 3.7.3 sees the reintroduction of the bulk compiler plugin, which will help out here!

I just attached a small report that demonstrates this problem in our application.

Hi Lucian, I am using iReport 3.7.2 to compile the JRXML and it is set to "Last Version", which I must assume is 3.7.2. However, we have many subreports, so I cannot guarantee that every sub report has been compiled in this version. Do you think this could be the problem? If so, I expect to get some kind of incompatible version exception when one of these reports is reached. Regards, Steve.

Thanks for the tip! We decided in the end that the alphabetical sorting was logical for us as although the data has a specific order, each column represents a different group of this data and the content can vary, so it doesn't matter which order the rows are printed in. In this case, it may as well be sorted alphabetically. I will keep this example in mind for the future though!

Hi Teodor, Thanks for your feedback. It seems we have some things to look at in our report templates. I have never come across this problem of overlapping elements and I don't remember reading anything about this in the documentation or javadoc; is this documented somewhere in case I need further help? It will take some time to implement your suggestions in our templates, but feel free to close this issue report. I have made a separate issue report of point 6 (issue #4468). Best Regards, Steve Chamberlain.

Ok, great. If I come across additional information that might help you diagnose the issue, I will post it there. Regards, Steve.

Hi Jasper Team, I have just downloaded and started to use Jasper Reports 3.5.3. Our main motivation for upgrading (besides bug fixes) are in order to use the new DOCX exporter. However, it seems that the documents produced cannot be opened by Word 2007. It appears that the document is missing a semicolon somewhere. I have attached the .docx report, the .jasper source I used to generate it and a screenshot of the error in Word. Is this a known issue? Best Regards, Steve Chamberlain.

Just a quick observation, the 3.5.3 release does not seem to be in the Maven central repository; will it be deployed there soon? Otherwise I will have to deploy it to our local repository. <a href="http://www.linkedin.com/in/stevechamberlain" ><img src="http://www.linkedin.com/img/webpromo/btn_viewmy_160x25.gif" width="160" height="25" border="0" alt="View my profile on LinkedIn"></a>

Hi Teodor, Thanks for the update, we will test out the new release soon. Best Regards, Steve.

Great! I look forward to testing the new functionality. Regards, Steve Chamberlain.

Interesting! Can you tell me when the new release is planned for? How about the DOCX export, has this been thoroughly tested with production level reports for layout issues?

As a user of Jasper Reports, our customers require that these reports be available in an editable and usable document format, be it RTF, DOC or DOCX. We have used the standard Jasper Reports exporters, but the documents they produce are simply not usable enough for our customers (RTF for example produces huge documents which crash Word 2007 http://jasperforge.org/plugins/mantis/view.php?id=3562). We have been working alongside Aspose in order to find a solution to these problems. We would like also to see these features implemented in JasperReports as soon as possible.

Hi Jasper Experts, I have an optimisation question regarding RTF reports generated by Jasper Reports. I have a relatively large report (120+ pages). These reports can be quite a bit larger. On each page there is a company logo in the top right hand corner. Information is represented in tables built out of static text and text field elements with borders to represent the cells. This all looks great in the report previewer and when exported to PDF. However, when I export to RTF the file size can be huge (24Mb or more). This causes Microsoft Word 2007 to crash when I try to open it. By overriding the JRRtfExporter class, I have disabled writing the cell borders to the RTF file and the size is reduced by 10Mbs. If I disable the graphics as well, my report shrinks down to less than 3Mb. However, this means the report no longer looks the same as the preview. We require the company logo to be printed on each page. I have been looking through the RTF 1.6 specification (used by the JRRtfExporter class) and I have not found a good way to export the raw image data and simply refer to that data on each page. Currently our graphics data is exported for EVERY page, which is a huge waste of space in the final RTF file as each instance of this data represents the same graphic. Does anybody have any good suggestions for optimising our report templates for RTF, or modifying the export routines so that we achieve a usable (i.e. as close to the preview as possible) result in reasonably sized (i.e. non-Word crashing) report files? RTF is a popular format, as the file can be modified in Word outside of our application when circumstances require it.

Hi All, I am having this same problem. I am using JasperReports version 3.1.0 and I also use iText 2.1.4 in my Maven based project. I expected that these versions would include this fix, but I am also getting exceptions like: java.lang.RuntimeException: The name '[our link name]' has no local destination. Should I be using different versions of these libraries?