bz3x

YES! Thank you Olga.

Correction: column header and column footer were not the appropriate bands for this report. I'm now using "title" and "last page footer". The main question now is: How to force a page break when there is only space for the title but not for any records, so that the whole subreport starts on a new page?

Dear community, I've been struggling with what seems like a simple issue. I have a report with three subreports. When the first subreport has just enough records in the detail section to fill up almost the entire first page, and at the bottom of the first page there's just enough room for the header of the second subreport (but not the details section), that subreport shows only the column header and the column footer but not the data section. In short: how can I force the second subreport to display the column header and column footer only if the detail section is displayed? I've tried setting the "Print when" of subreport's column footer to !$V{sumTotal}.isNaN() (sumTotal is a variable I use to show data in the footer). That works for the footer but the subreport header remains. And I can't use the same trick as with the footer because the sumTotal variable isn't set yet. The issue is clearer in the attached report. Thanks for any pointers or solutions!

Horizontal print order? Where the details section repeats horizontally? No, in this report the details section repeats vertically like a more standard report. Only that there's so much data to display for each detail that the report needs to be two pages wide. Is this possible? Thanks for all suggestions and tips!

Hi everyone, I'd like to create a PDF report that is two (or three) pages wide. The structure of the report is fairly simple, just a detail section with any number of objects to repeat, only that the detail section should span horizontally. Is there a way to do this? I thought about creating two separate reports, but given that some records might stretch, there's no way to guarantee that the "rows" will match up on the pages. Thanks for your advice!

It's always difficult to locate problems in an application built on multiple frameworks or components. In this case the problem in the end wasn't related to reporting, only that the problem only showed up in the reports. Aside from the issue of escaping the unicode characters in the property files, the user-input data wasn't stored as unicode at all, but in HTML encoding. So I simply ran a HTML unencoding function on the text in my POJO-JRDataSource wrapper, as follows. Hopefully this will be of help to the next person who runs into this issue. Code:private String convertHtmlToUnicode(String html) { int begU = html.indexOf(""«»); if (begU==-1) { return html; } else { String before = html.substring(0,begU); int endU=html.indexOf(";", begU); char uni = (char)Integer.parseInt(html.substring(begU+2,endU)); String after = html.substring(endU+1, html.length()); return before+uni+convertHtmlToUnicode(after); } }

I get it. I ran native2ascii and was able to see the $R{} string correctly in both the unicode example and my real-world application (and both the PDF and Excel views of my report!). The JSPs, which worked even before escaping the characters, work fine with the new properties file too. This leaves the problem of the $F{} strings. For a JRDataSource I'm using a wrapper around a Collection or a Map - (taken from somewhere on these forums, see code below). Apparently either this class or the report doesn't realize that the text is unicode, since it shows me "oıxş". Any ideas on the best place to attack this? In the class? On the report? Thanks again for your input!! Code:import java.lang.reflect.Method; import java.util.Collection; import java.util.HashMap; import java.util.Iterator; import java.util.Map; import net.sf.jasperreports.engine.JRDataSource; import net.sf.jasperreports.engine.JRException; import net.sf.jasperreports.engine.JRField; import org.apache.commons.beanutils.PropertyUtils; public class ReportSource implements JRDataSource { protected HashMap fieldsToIdxMap=new HashMap(); protected Iterator iterator; protected Object currentValue; public ReportSource(Collection list) { this.iterator = list.iterator(); } public ReportSource(Map list) { this.iterator = list.values().iterator(); } private Object nestedFieldValue(Object object, String field) { Object value = null; if (field.indexOf("__"«»)>-1) { try { Method nestedGetter = PropertyUtils.getReadMethod(PropertyUtils.getPropertyDescriptor(object, field.substring(0,field.indexOf("__"«»)))); Object nestedObject = nestedGetter.invoke(object, null); value = nestedFieldValue(nestedObject, field.substring(field.indexOf("__"«»)+2, field.length())); } catch (Exception ex) { ex.printStackTrace(); } } else { try { Method getter = PropertyUtils.getReadMethod(PropertyUtils.getPropertyDescriptor(object, field)); value = getter.invoke(object, null); if(Collection.class.isAssignableFrom(getter.getReturnType())) { return new ReportSource((Collection)value); } if (Map.class.isAssignableFrom(getter.getReturnType())) { return new ReportSource((Map)value); } } catch (Exception ex) { ex.printStackTrace(); } } return value; } public Object getCurrentValue() throws JRException { return currentValue; } public boolean next() throws JRException { currentValue = iterator.hasNext() ? iterator.next() : null; return currentValue != null; } public Object getFieldValue(JRField field) throws JRException { return nestedFieldValue(currentValue, field.getName()); } }

Thanks for replying! I can reproduce a similar error by modifying the Unicode sample report, adding two new fields. The first just shows $P{TurkishText} and works correctly just like the Cyrillic, Greek, Arabic and Hebrew examples. The second is supposed to show $R{test}, and I've added a properties file saved in UTF-8. Attached is the report. I'm inputting the same value for $P{TurkishText} and $R{test}, but the result in the PDF is vastly different: $P{TurkishText} shows "oıxş" (correct) while $R{test} shows "oıxÅ". Apparently the error is about how the report gets the text. The fact that in my real-world application (based on Spring) the $R{} and the $F{} fields show different errors for the same strings leads me to believe that Spring (or rather, my configuration of Spring) passes the report source and the properties file in two different ways, neither of them are working though. Thanks for any thoughts! [file name=UnicodeReport.jrxml size=11418]http://www.jasperforge.org/components/com_joomlaboard/uploaded/files/UnicodeReport.jrxml[/file]

I dumped my previous approach of using a unicode font - the 22Mb Unicode font was too much. So instead I'm testing a string that contains Turkish characters (ÅŸlkjpoıu), only two of which aren't found in the normal ASCII set. The field is set to use a Turkish font, with PDF-encoding Identity-H (Unicode horizontal), and am embedding the PDF font. The report compiles and even displays, so I assume the font is actually being embedded. The result? When the string is taken from a field ($F{foo}), I see şlkjpoıu, and when the string is taken from a properties file ($R{foo}), I see "lkjpou" - the special characters are missing. Hasn't anyone run into this problem? Anyone with experience, please help! bz3x

Hi, this is the first time I'm trying to add i18n to some reports I created with iReport (2.0.4) in a Spring application. My starting point is that when the report tries to display some Hebrew characters (שלו×), the output is "של", which I presume is the unicode encoding for the first two letters. Eventually I will be adding Russian, Turkish, Portugese and Arabic as well. I've looked through the documentation and forums but haven't found any good, clear descriptions of how to address this. So far, I've 1) set the textfield to use the Arial Unicode MS font, 2) set PDF-encoding to Identity-H (Unicode horizontal) and 3) have experimented both options for "PDF Embedded". When I run the report in the application I get the following: Java heap space java.lang.OutOfMemoryError: Java heap space at java.util.Arrays.copyOf(Unknown Source) at java.io.ByteArrayOutputStream.write(Unknown Source) at com.lowagie.text.pdf.RandomAccessFileOrArray.InputStreamToArray(RandomAccessFileOrArray.java:130) at com.lowagie.text.pdf.RandomAccessFileOrArray.(RandomAccessFileOrArray.java:97) at com.lowagie.text.pdf.TrueTypeFont.process(TrueTypeFont.java:577) at com.lowagie.text.pdf.TrueTypeFontUnicode.(TrueTypeFontUnicode.java:95) at com.lowagie.text.pdf.BaseFont.createFont(BaseFont.java:394) at com.lowagie.text.pdf.BaseFont.createFont(BaseFont.java:342) at com.lowagie.text.FontFactory.getFont(FontFactory.java:225) at net.sf.jasperreports.engine.export.JRPdfExporter.getFont(JRPdfExporter.java:1701) at net.sf.jasperreports.engine.export.JRPdfExporter.writePageAnchor(JRPdfExporter.java:588) at net.sf.jasperreports.engine.export.JRPdfExporter.exportReportToStream(JRPdfExporter.java:528) at net.sf.jasperreports.engine.export.JRPdfExporter.exportReport(JRPdfExporter.java:322) at org.springframework.ui.jasperreports.JasperReportsUtils.render(JasperReportsUtils.java:113) at org.springframework.web.servlet.view.jasperreports.AbstractJasperReportsSingleFormatView.renderReport(AbstractJasperReportsSingleFormatView.java:100) at org.springframework.web.servlet.view.jasperreports.JasperReportsMultiFormatView.renderReport(JasperReportsMultiFormatView.java:208) at org.springframework.web.servlet.view.jasperreports.AbstractJasperReportsView.renderMergedOutputModel(AbstractJasperReportsView.java:578) at org.springframework.web.servlet.view.AbstractView.render(AbstractView.java:251) at org.springframework.web.servlet.DispatcherServlet.render(DispatcherServlet.java:1160) at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:901) at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:809) at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:476) at org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:431) at javax.servlet.http.HttpServlet.service(HttpServlet.java:689) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) Is this because the font is too large? If I use a Hebrew font I will need to somehow change fonts at runtime depending on the locale for other languages. Or is there something else going on? I'd appreciate any comments from someone with experience with this. Thanks!

Don't know why, but a nice clean reboot solved the problem. Eclipse? iReport? Who knows. :S

I've finally gotten around to moving from iReport 0.5 (!) to 2.0.4 for a Spring application. As expected, I'm getting the following error: java.io.InvalidClassException: net.sf.jasperreports.engine.base.JRBaseReport; local class incompatible: stream classdesc serialVersionUID = 607, local class serialVersionUID = 10200 All the comments and forum message I've seen say to copy the jasperreports.jar file from the new iReport to my application. But I've done that and still am getting the error. I've also tried to play with iReport's compatibility feature, setting compatability to 0.6 and recompiling. I wouldn't expect that to work either (my earlier version was 0.5), but I would expect that the error message show a different "local class serialVersionUID", but it stays the same. Any ideas? Experience? Will be happy to post code/configuration if you tell me where to look. Thanks! Post edited by: bz3x, at: 2008/01/28 09:17