nomike

Until now, we use the distribution-zip of jasper reports with all it's libraries. However for debugging purpose this is no optimal solution, as there are no sources or javadoc attached. So, as I try to get sources and documentation for those, i was wondering if it's a good idea to update all the libraries to the most recent version. Could you recommend this, or is there a good reason why jasper reports comes shipped with a lot of outdated libraries? Are there specific ones which are known to cause problems with the most recent version? Thx in advance! nomike aka Michael Postmann

Hi! I'm using ant to compile my reports. This is my Taskdef: Code:<taskdef name="jrc" classname="net.sf.jasperreports.ant.JRAntCompileTask" classpathref="module.compiled.classpath"> </taskdef> and this is the call: Code:[code]<jrc srcdir="reports" destdir="reports"> but this produces heavy loads of debug output. Is there a way to reduce the output to info/warn/error/fatal messages only? thx in advance nomike aka Michael Postmann

Hi! I'm developing an application which uses JPOX 1.2 (JDO 2.1) as persistence layer. Is it possible to use JPOX/JDO and the JDO-Query Language inside of jasperReports? thx in advance nomike aka Michael Postmann

I have a single Field selected. When I change the width in the Properties Panel on the right, and press enter the size of the field changes. When there are multiple different sized Fields selected, and I enter a different size, and press enter nothing happens. From now on, when I select a single Field with e.g. width 100 and enter 120 and press Return nothing happens. When I select a different item and select the previous field again, it still shows 100 as width. I need to resize any item with the mouse (doesn't have to be the specific field) once to get the functionality of beeing able to set the width via the properties again. I hope you understand what I mean. nomike aka Michael Postmann

One possible "Workaround" is to use this Button. However it removes all borders and margins. nomike aka Michael Postmann size=213]http://www.jasperforge.org/components/com_joomlaboard/uploaded/images/ireport_bug.png

Same problem here. I'm using the german version of 1.3.0 but since I'm used to work in the english version, i'm missing it too. For now I'm switching to iReport 1.2.8 frequently. nomike aka Michael Postmann

I filed in a Bug now. See here for details: http://jasperforge.org/sf/go/artf1897?nav=1

BTW: The same applies to other special characters as well (e.g. $, +, etc.) nomike aka Michael Postmann

Symptom: When I open a Report with a "#" char in it's filename in iReport and select "Build --> Compile" in the menu, I get the following error: Code:Compiling to file... C:ressys40ReportsA4CommonCouponNightcouponnightcoupon#test.jasper -> C:ressys40ReportsA4CommonCouponNightcouponnightcoupon#test.java Errors compiling C:ressys40ReportsA4CommonCouponNightcouponnightcoupon#test.jasper! it.businesslogic.ireport.ReportClassLoader@1be2b55 0 [Thread-7] ERROR digester.Digester - Parse Error at line 19 column 29: Attribute value "nightcoupon#test" of type NMTOKEN must be a name token. org.xml.sax.SAXParseException: Attribute value "nightcoupon#test" of type NMTOKEN must be a name token. at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source) at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.dtd.XMLDTDValidator.validateDTDattribute(Unknown Source) at org.apache.xerces.impl.dtd.XMLDTDValidator.addDTDDefaultAttrsAndValidate(Unknown Source) at org.apache.xerces.impl.dtd.XMLDTDValidator.handleStartElement(Unknown Source) at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentScannerImpl$ContentDispatcher.scanRootElementHook(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) at org.apache.commons.digester.Digester.parse(Digester.java:1647) at net.sf.jasperreports.engine.xml.JRXmlLoader.loadXML(JRXmlLoader.java:238) at net.sf.jasperreports.engine.xml.JRXmlLoader.loadXML(JRXmlLoader.java:225) at net.sf.jasperreports.engine.xml.JRXmlLoader.load(JRXmlLoader.java:213) at net.sf.jasperreports.engine.xml.JRXmlLoader.load(JRXmlLoader.java:167) at net.sf.jasperreports.engine.xml.JRXmlLoader.load(JRXmlLoader.java:151) at net.sf.jasperreports.engine.JasperCompileManager.compileReportToFile(JasperCompileManager.java:107) at it.businesslogic.ireport.IReportCompiler.run(IReportCompiler.java:510) at java.lang.Thread.run(Thread.java:619) net.sf.jasperreports.engine.JRException: org.xml.sax.SAXParseException: Attribute value "nightcoupon#test" of type NMTOKEN must be a name token. at net.sf.jasperreports.engine.xml.JRXmlLoader.loadXML(JRXmlLoader.java:242) at net.sf.jasperreports.engine.xml.JRXmlLoader.loadXML(JRXmlLoader.java:225) at net.sf.jasperreports.engine.xml.JRXmlLoader.load(JRXmlLoader.java:213) at net.sf.jasperreports.engine.xml.JRXmlLoader.load(JRXmlLoader.java:167) at net.sf.jasperreports.engine.xml.JRXmlLoader.load(JRXmlLoader.java:151) at net.sf.jasperreports.engine.JasperCompileManager.compileReportToFile(JasperCompileManager.java:107) at it.businesslogic.ireport.IReportCompiler.run(IReportCompiler.java:510) at java.lang.Thread.run(Thread.java:619) Caused by: org.xml.sax.SAXParseException: Attribute value "nightcoupon#test" of type NMTOKEN must be a name token. at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source) at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.dtd.XMLDTDValidator.validateDTDattribute(Unknown Source) at org.apache.xerces.impl.dtd.XMLDTDValidator.addDTDDefaultAttrsAndValidate(Unknown Source) at org.apache.xerces.impl.dtd.XMLDTDValidator.handleStartElement(Unknown Source) at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentScannerImpl$ContentDispatcher.scanRootElementHook(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) at org.apache.commons.digester.Digester.parse(Digester.java:1647) at net.sf.jasperreports.engine.xml.JRXmlLoader.loadXML(JRXmlLoader.java:238) ... 7 more Compilation running time : 172 This seems to be a bug! nomike aka Michael Postmann PS: I'm using iReport and JasperReports v. 1.2.8

Well, basically your solution sounds good, but it has two problems which make it unuseable for us: First of all, the reports frequently change. So if we use a jar file and a classloader to load the reports we need to restart the application if a report changes which is inacceptable. And secondly the all nice and good EJB Spec (*grmmmml* :angry: ) says: The enterprise bean must not attempt to create a class loader; obtain the current class loader; set the context class loader; set security manager; create a new security manager; stop the JVM; or change the input, output, and error streams. These functions are reserved for the EJB container. Allowing the enterprise bean to use these functions could compromise security and decrease the container’s ability to properly manage the runtime environment. thx, but I think I have to find another solution... :( nomike aka Michael Postmann

Thx for your support! The thread thingy sounds good to me. But I don't know what you mean/what is a "report virtualizer"?!? I have a directory on Disk which contains our .jrxml and .jasper files. I then do Code: public JasperPrint printCoupon(CouponVO coupon, String mapping, Integer userID) throws FinderException { JRDataSource dataSource = new JRMapArrayDataSource(new Object[1]); HashMap<String, Object> map = new HashMap<String, Object>(); CustomerVO cvo = getCustomerFromSomewhere(); KassaArticleVO kavo = getArticleFromSomewhere(); CouponTypeVO tcvo = getCouponTypeFromSomewhere(); map.put("amout", coupon.getAmount()); map.put("bookingCode", tcvo.getBookingCode()); map.put("buyerCity", cvo.getCity()); map.put("buyerFirstName", cvo.getFirstName()); /*...*/ map.put("TXT_copy", "Copy"«»); map.put("coupon", null); map.put("user", null); try { String reportName = getReportFileName(); // "C:\Reports\sampleReport.jasper" return JasperFillManager.fillReport(reportName, map, dataSource); } catch (JRException ex) { logger.fatal(ex); return null; } } This makes JasperReport load the .jasper file using java.io.File and others. And Java.io.* must not be used in EJB according to EJB specs... nomike aka Michael Postmann Post edited by: nomike, at: 2006/10/12 13:42

Hi! I'm re-developing our existing business application using J2EE. We use JasperReport to generate reports with 4000+ Pages constructed using 100.000+ DB Records including Dependencies. So they are quite Huge. We are currently using a distributed Client Application with a small-footprint-server where every client has direct DB-Access. Now as I need to reimplement the Application to make it use J2EE (EJB 2.1) I wanted to move the report-generation to the ApplicationServer (JBoss in our case) and created a Session Bean. It creates a Report and returns a JasperPrint object which is then displayed and printed on the swing-client. However, jasper utilizes java.io a lot and does threading too, which are both permitted by the J2EE-Spec. So how could I generate jasperreports in a performant-way without violating EJB Specs and without doing it on the client? thx in Advance nomike aka Michael Postmann PS: It seems to work as an EJB-Bean, but I don't know if I should expect to run into problems... Post edited by: nomike, at: 2006/10/12 10:17