lcourtin

After some weeks of use, there is no problem with the 3.6.0 version.

Hello, http://jasperforge.org/plugins/mantis/view.php?id=3832 Thank you very much for your availability, I am eager to test the fix. Best regards, Laurent Courtin

Hello, I have tested the version 3.5.0 and I faced with the same problem. I used the work arround of pbakker before the call "JasperFillManager.fillReport" ( http://jasperforge.org/plugins/espforum/view.php?group_id=102&forumid=103&topicid=54774 ) This acts on "ExtensionsEnvironment.getExtensionsCacheKey()" and the registry in "DefaultExtensionsRegistry" (method getExtensions(...)). Code: Best regards, Laurent Post Edited by Laurent Courtin at 04/17/09 13:24

Thanks for the answer. Unfortunatly I have already tried this sort of manipuation on URLClassLoader instance, and I have had any sucess. In my last try, I had put the directory of the reports on the (dynamic) ckasspath, and I load the report with JRLoader.loadObjectFromLocation(...) I admit that the problems of class loader seem rather "magical". Can I use your wording for the text of the problem? Summary:No query executer factory registered error. Decription: JR should work as before and not rely on the fact that the JR classes/resources are present on the context classloader Best regards, Laurent Courtin

Hello, We currently use JasperReport 3.0.0 and we try to change with JasperReport 3.1.3. We have this error with some reports (not all of them !) : The cause seems to be a class loader problem: We use a URLClassLoader in our application. (the archives are loaded dynamicaly) If we change this desing there is no problem. (we put all the archives in the JVM loading classpath) I have tried to put the directory of the reports in the classapth and some other manipulation on class loader with no success. Do you have any ideas ? Best regards, Laurent Courtin The error stack trace: net.sf.jasperreports.engine.JRRuntimeException: No query executer factory registered for the 'sql' language. at net.sf.jasperreports.engine.util.JRQueryExecuterUtils.getQueryExecuterFactory(JRQueryExecuterUtils.java:67) at net.sf.jasperreports.engine.fill.JRFillDataset.createQueryDatasource(JRFillDataset.java:664) at net.sf.jasperreports.engine.fill.JRFillDataset.initDatasource(JRFillDataset.java:588) at net.sf.jasperreports.engine.fill.JRBaseFiller.setParameters(JRBaseFiller.java:1212) at net.sf.jasperreports.engine.fill.JRBaseFiller.fill(JRBaseFiller.java:842) at net.sf.jasperreports.engine.fill.JRBaseFiller.fill(JRBaseFiller.java:791) at net.sf.jasperreports.engine.fill.JRFiller.fillReport(JRFiller.java:63) at net.sf.jasperreports.engine.JasperFillManager.fillReport(JasperFillManager.java:402) ....

Hello, We evaluate iReport-nb-3.1.1-plugin (we use iReport-3.0.0 for the moment). We have a question : how to choose the compiler directory ? In iReport-nb-3.1.1 the jasper file is created in the same directory as the jrxml files, but we want to choose the directory. This was a option in iReport-3.0.0 Best Regards, Laurent Courtin