Problems with JasperReport After Servoy Update

Classic Servoy
1

I am running the latest servoy 4.1.2. When updating servoy it causes problems with reports . After updating to Servoy 4.1.2 I had to roll back to servoy-jasperreport plugin 2.1.4 and use jasperreport 3.0.0. Has anyone else had problems with this? It is a nightmare trying to figure out the right config so reports will run. This problem occurs almost always in the client. The developer seems to be less problematic and will run newer releases of the plugin and jasperreport. After alot of testing the above config was able to get the reports working. How might I speed up this process after updating servoy in the future. I had to really dig to get partial answers to a very tricky problem.

2

Hi ALL,
I have had a run in with this as well.
Note that the library for the JasperReports that works with the plugin is version 3.0.x
If you try to use JasperReports version 3.5.0 you might have a problem.

There is a known issue that I recorded in the Google code base for the Jasper Reports Plugin. I had to roll back to version 2.1.4 as well.
However, I am now trying the 2.1.6_beta version and am inserting some test points to the exceptions (to get better debug information out).
I have had success with version 2.1.6_beta - but this might not be the next version out!

Hints:
Check the reports directory on the server admin page for the plugin - ensure it is not null!
DO put a try…catch block around the call to the jasper reports plugin to find out a little more. Like this example here:

var pluginVersion = plugins.jasperPluginRMI.pluginVersion;
var verSub = pluginVersion.substr(0 ,5);
var repDir = plugins.jasperPluginRMI.reportDirectory;
var servoyServerDir = plugins.jasperPluginRMI.servoyServerDirectory;//NOTE THIS IS MY ADDED ENHANCEMENT in my OWN version - comment out

try {
	if ( verSub.equalsIgnoreCase('2.1.4') || verSub.equalsIgnoreCase('2.1.5') ){
		result = plugins.jasperPluginRMI.jasperReport(serverName, reportName, varOutput, outputFormat, reportParameters );
		}
	else {
		application.output("using locale as last argument, report= " + reportName + " output= " + varOutput + " format= " + outputFormat + " repParams= " + reportParameters + " repDir= " + repDir + " locale = " + locale);
		result = plugins.jasperPluginRMI.jasperReport(serverName, reportName, varOutput, outputFormat, reportParameters, locale );
		}
	} catch (e) {
	msg = "DEBUG: Exception from plugin: "
	if (e == undefined) {
		msg += "exception 'e' is undefined";
	}
	else if (e.message == undefined){
		msg += "exception message is undefined";
	}
	else {
		msg += "message: <" + e.message + ">";
	}

	application.output(	msg );

More hints:
If you developed a report using iReports 3.5.0 try using the “.jasper” file (compiled form of the “.jrxml”) with the plugin version 2.1.4 - I have found this works for most reports of mine. This will also skip the internal compile within the plugin.

Suffice it to say that it is VERY frustrating :x not knowing the cause.
Keep in mind that you should look into the Google code issues as well as this forum.

It would be helpful to us all to know what config changes finally worked for you!

Let me know if this helps.
Tom

3

For now I just went ahead and used servoy-jasperreport plugin 2.1.4 and jasperreport 3.0.0. This at least gets all my reports working within my solution. However, I am able to use Ireport 3.1.3. With this configuration all of my reports are working properly.