2006 IR Open Dicussion Posted August 26, 2006 Share Posted August 26, 2006 By: eric - greatmaster generating reports with the CVS version 2006-02-06 04:33 When i want to generate PDF from the CVS version of JR i have this exception : net.sf.jasperreports.engine.JRException: No query executer factory class registered for null queries. Create a propery named net.sf.jasperreports.query.executer.factory.null.> net.sf.jasperreports.engine.JRException: No query executer factory class registered for null queries. Create a propery named net.sf.jasperreports.query.executer.factory.null. Is anyone knows what is it about ? Thanks Eric By: Lucian Chirita - lucianc RE: generating reports with the CVS version 2006-02-06 05:02 It seems that no language is set for the report query. How are you creating report designs (JRXML or API)? Are the reports compiled using the same CVS version? Regards, Lucian By: eric - greatmaster RE: generating reports with the CVS version 2006-02-06 05:55 I use JRXML designed with ireport. These reports are generated and compiled in a web application that uses jasperreports.jar. It is 1.1.1 compliant. So i replaced jasperreports-1.1.1.jar by the new one from CVS. The behaviour seems not to be the same beetwen the 1.1.1 version and the CVS one. When is the query language is defined ? in the jrxml ? Eric By: Lucian Chirita - lucianc RE: generating reports with the CVS version 2006-02-06 06:22 The query language can be specified in the JRXML, but it's not mandatory and it defaults to "sql". Are you compiling the reports using the CVS version? By: eric - greatmaster RE: generating reports with the CVS version 2006-02-06 06:51 Yes i use the CVS version to compile reports. So why language is set to null ? I think the web app need some changes because with the jasperreport.jar from CVS i have the following exception when retrieving a crosstab Report: java.io.InvalidClassException: net.sf.jasperreports.crosstabs.design.JRDesignCrosstab$Pair; local class incompatible: stream classdesc serialVersionUID = 7557197778531471908, local class serialVersionUID = 1 Eric By: Lucian Chirita - lucianc RE: generating reports with the CVS version 2006-02-06 07:26 You have to versions of the JR library. That's why you get the incomptabile class exception and the null query language. Make sure you use the same library version everywhere across your application. Regards, Lucian By: Lucian Chirita - lucianc RE: generating reports with the CVS version 2006-02-06 07:27 You have two versions of the JR library. That's why you get the incomptabile class exception and the null query language. Make sure you use the same library version everywhere across your application. Regards, Lucian By: eric - greatmaster RE: generating reports with the CVS version 2006-02-06 08:44 I have only one version of the jasperreports.jar within the context of the application ... (in the lib directory) I recompiled all the classes with the new jar too ... How could it cause problems ? Eric By: Lucian Chirita - lucianc RE: generating reports with the CVS version 2006-02-07 00:51 I don't think you can get incompatible class exceptions if you have a single version of the class. At which point do you get the JRDesignCrosstab$Pair exception? Where are you loading the design object from? Regards, Lucian By: eric - greatmaster RE: generating reports with the CVS version 2006-02-07 02:03 Hi, In fact the webapp save report Design and object reports in a DB. So i need to reload them with the good version of jasperreports. Now the problem is on the serialization of JasperDesign. This exception appear : java.io.NotSerializableException: net.sf.jasperreports.engine.design.JRDesignDataset$1 When changing to actual JR-1.1.1 all is OK. Any idea ? Eric By: Lucian Chirita - lucianc RE: generating reports with the CVS version 2006-02-07 02:24 You are using an old CVS snapshot. This was fixed some weeks ago. Refresh your source from CVS, or get the 1.2.0 release sources and the error will be gone. HTH, Lucian By: eric - greatmaster RE: generating reports with the CVS version 2006-02-07 02:49 Ok ... It works fine now with the 1.2.0 release ... Thanks a lot Lucian. Eric Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now