skrpc

I have rebuilt jr 4.1.1 from the svn trunk and replacing the original jasperreports-4.1.1.jar in ireport/modules/ext with my new build does enable me to both open a report that previously failed due to a table and successfully compile the report which had the groovy formatting issue (bug #5410). I will go through all my reports and recompile them in 4.1.1 tomorrow (Thursday) but initial testing shows the updates you applied to svn trunk does seem to have fixed both the problems I was having (bugs #5410 and #5411). Thanks Scott

I have uploaded a complete jrxml called roman_contact_list.jrxml and it fails at line 198. It fails at this line in both iReports 4.1.1. and Jaspersoft Studio 1.0.1 Thanks, Scott.

I have now installed Jaspersoft Studio 1.0.1 and this also fails to load reports with tables at the same location. I have attached a file of the jrxml (table_jrxml.txt) and the line the designers error on is line 16 which is the the first instance of the element close tag .

I have had this issue in versions of JasperReports for as long as I can remember (I am now using 4.1.1). The groovy statement $F{duration} == null ? 0 : $F{duration} does not seem to work, the output of the text field is the word "null", the field value is null because if I select the option Blank when Null the output is indeed blank. Seems a basic test but have found that it only seems to work for string values, any numeric based value cannot be tested for null and the output defaulted to another value. For example test if a field is null in the database and output No otherwise output "Yes" so you would assume the statement $F{intval} == null ? "No" : "Yes" would be ok but no, when the field in the database has a null value the output is "null" and not "No" Comments ??

All my reports originally written in 4.0.1 will not load, I tracked this down to reports that contain a table so I delete the table and then recreate the table, and the report compiles and I can run the report. However, if I the remove the report from the designer and reload the reports fails to load with the same error. It would appear that 4.1.1 does not support the loading of tables. I have tried tables in a few different bands and the same always occurs. The xml that if removed enables the designer to open and display the report is <componentElement> <reportElement key="table 1" x="152" y="26" width="180" height="20"/> <jr:table xmlns:jr="http://jasperreports.sourceforge.net/jasperreports/components" xsi:schemaLocation="http://jasperreports.sourceforge.net/jasperreports/components http://jasperreports.sourceforge.net/xsd/components.xsd"> <datasetRun subDataset="Selection"> <connectionExpression><![CDATA[$P{REPORT_CONNECTION}]]></connectionExpression> </datasetRun> <jr:column width="90"> <jr:detailCell height="20"> <textField> <reportElement x="0" y="0" width="90" height="20"/> <textElement/> <textFieldExpression><![CDATA[$F{selection_prompt}]]></textFieldExpression> </textField> </jr:detailCell> </jr:column> <jr:column width="90"> <jr:detailCell height="20"> <textField> <reportElement x="0" y="0" width="90" height="20"/> <textElement/> <textFieldExpression><![CDATA[$F{selection_data}]]></textFieldExpression> </textField> </jr:detailCell> </jr:column> </jr:table> </componentElement> The error reported is Error loading the report template Message: net.sf.jasperreports.engine.JRException: org.xml.sax.SAXParseException; lineNumber: 184; columnNumber: 24; Error at line 184 char 24: null Level: SEVERE Stack Trace: org.xml.sax.SAXParseException; lineNumber: 184; columnNumber: 24; Error at line 184 char 24: null net.sf.jasperreports.engine.xml.JRXmlLoader.loadXML(JRXmlLoader.java:247) net.sf.jasperreports.engine.xml.JRXmlLoader.loadXML(JRXmlLoader.java:230) net.sf.jasperreports.engine.xml.JRXmlLoader.load(JRXmlLoader.java:218) com.jaspersoft.ireport.designer.JrxmlLoader.reloadJasperDesign(JrxmlLoader.java:87) com.jaspersoft.ireport.designer.JrxmlVisualView.run(JrxmlVisualView.java:505) org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:572) org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:997) Error at line 184 char 24: null org.apache.commons.digester.Digester.createSAXException(Digester.java:2919) org.apache.commons.digester.Digester.createSAXException(Digester.java:2945) org.apache.commons.digester.Digester.endElement(Digester.java:1133) net.sf.jasperreports.engine.xml.JRXmlDigester.endElement(JRXmlDigester.java:183) com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(AbstractSAXParser.java:604) com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.endElement(XMLSchemaValidator.java:825) com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanEndElement(XMLDocumentFragmentScannerImpl.java:1759) com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2915) com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:625) com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:116) com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:488) com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:812) com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:741) com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:123) com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1208) com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:525) org.apache.commons.digester.Digester.parse(Digester.java:1647) net.sf.jasperreports.engine.xml.JRXmlLoader.loadXML(JRXmlLoader.java:243) net.sf.jasperreports.engine.xml.JRXmlLoader.loadXML(JRXmlLoader.java:230) net.sf.jasperreports.engine.xml.JRXmlLoader.load(JRXmlLoader.java:218) com.jaspersoft.ireport.designer.JrxmlLoader.reloadJasperDesign(JrxmlLoader.java:87) com.jaspersoft.ireport.designer.JrxmlVisualView.run(JrxmlVisualView.java:505) org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:572) org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:997) null net.sf.jasperreports.components.table.StandardColumn.addGenericElementToHeader(StandardColumn.java:123) net.sf.jasperreports.components.table.StandardColumn.setDetailCell(StandardColumn.java:97) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) java.lang.reflect.Method.invoke(Method.java:616) org.apache.commons.beanutils.MethodUtils.invokeMethod(MethodUtils.java:283) org.apache.commons.digester.SetNextRule.end(SetNextRule.java:216) org.apache.commons.digester.Rule.end(Rule.java:230) org.apache.commons.digester.Digester.endElement(Digester.java:1130) net.sf.jasperreports.engine.xml.JRXmlDigester.endElement(JRXmlDigester.java:183) com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(AbstractSAXParser.java:604) com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.endElement(XMLSchemaValidator.java:825) com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanEndElement(XMLDocumentFragmentScannerImpl.java:1759) com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2915) com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:625) com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:116) com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:488) com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:812) com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:741) com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:123) com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1208) com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:525) org.apache.commons.digester.Digester.parse(Digester.java:1647) net.sf.jasperreports.engine.xml.JRXmlLoader.loadXML(JRXmlLoader.java:243) net.sf.jasperreports.engine.xml.JRXmlLoader.loadXML(JRXmlLoader.java:230) net.sf.jasperreports.engine.xml.JRXmlLoader.load(JRXmlLoader.java:218) com.jaspersoft.ireport.designer.JrxmlLoader.reloadJasperDesign(JrxmlLoader.java:87) com.jaspersoft.ireport.designer.JrxmlVisualView.run(JrxmlVisualView.java:505) org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:572) org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:997)

I have recently upgraded to JaperReports 4.1.1 and have noticed that my reports written using iReports 4.0.1 will no longer compile and the reason appears to be groovy expression formatting. A text field with a text field expression of $F{cell_phone} == null && $F{satellite_phone} != null ? $F{satellite_phone} : $F{cell_phone} fails but if I place all the code on one line it compiles ok. I aften use line break formatting so I can see all the expression without having to scroll or resize the window so this is a mjor annoyance. Any plans to fix this ??