Jasper report webclient

Classic Servoy
1

I posted an exception at Servoy Forge (Defect #416) almost three months ago.

Report compilation is not possible with the Servoy Webclient. => show stopper.

Still no reaction !! :shock: :cry:

Is this the price of open sourcing the Jasper Report plugin ?

Regards,

2

Still no respons on this ! :cry: :cry:

3

Hi Lambert,

This is working fine for me.
Can you check if the filename matches the name property on the 2nd line of the jrxml file?
So if you have a file ‘myReport.jrxml’ the name property should have ‘myReport’.

No match = no compilation in the plugin.
I’ve made this into a defect on ServoyForge as well, and got no response so far.

4

Hi Mark,

Thanks for helping out !

The filename is matching the name property so that is not my problem.
On Servoy Forge you see the resolving errors that come up when compiling…

Can you compile without errors our jrxml file with Servoy webclient (5.2.13 or 5.2.11) ?

Regards,

5

Hi Lambert,

sorry for the late reply.
I’m able to compile the jrxml file from a webclient v5.2.13

I’m using the latest version of the jasper plugin, extended with some jar’s which are needed for Groovy support etc.
Those don’t seem to be part of the current plugin anymore.

Maybe that’s what makes the difference…?

6

Hi Mark,

Is Groovy support deprecated in the current jasper report plugin ? Documentation about that ?

The compilation (of a Groovy report) runs ok in Smart client…

Regards,

7

not sure about that.

I just checked what I needed:

  • I run the latest 3.3.0b1 version of the plugin.
  • added the groovy-all-1.5.5.jar to the servoy_jasperreports folder.
  • changed the jnlp accordingly.

You can download the Groovy jar here: http://repo1.maven.org/maven2/org/codehaus/groovy/groovy-all/1.5.5/groovy-all-1.5.5.jar

Hope this will help.

8

Hi Marc,

In the Servoy Forge ChartNScript_Servoy_JasperReports_Plugin_v.3.3.0_b1.zip is the groovy-all-1.7.5.jar present and the jnlp is accordingly.

We use this version. It seems unlikely that is a problem introduced with 1.7.5. (No problem in Smart client)

Regards,