Project

General

Profile

Defect #733

Styles in Jasper prints via Servoy Plugin

Added by Luca Sceresini over 10 years ago. Updated about 10 years ago.

Status:
Resolved
Priority:
High
Start date:
09/11/2013
Due date:
% Done:

0%

Estimated time:
Browser (if web client):

Description

As suggested by Andrei Costache I tried to use the new version of Jasper Plugin which includes support for styles.
I modified my '.jrxml' file and added the line
<template><![CDATA[com.servoy.plugins.jasperreports.JasperReportsResourceLoader.loadStyle("databridge.jrtx")]]></template>
This are the paths defined on Servoy Server Admin Page:
directories.jasper.extra: /home/report/SY/styles/,/home/report/SY/images/
directory.jasper.report: /home/report/
('databridge.jrtx' is on the the folder /home/report/SY/styles/ and '.jrxml' file is in a subdirectory under '/home/report/').
When i tried to compile report on my developer it returns an error. This is the command line:
plugins.jasperPluginRMI.compileReport('avviso_arrivo_merce_a.jrxml');
the error returned is attached as 'a1.jpg'.
Otherwise, if I add a style reference and select my 'databridge.jrtx' it seems to work (it leaves me to compile report). I move file on server under the right directory but if I try to print via client it returns another error.
As told by Andrei I also tried to call directly the not-compiled file ('.jrxml') but it returns the same error which is returned if i try to compile it in my developer.
I hope that u can help me as soon as possible so I can implement styles in my reports (I use a lot of them and this will be a very useful feature!)

Write me if u need some other explanations ().

Best regards

Luca


Files

a1.jpg (171 KB) a1.jpg Error while compiling Luca Sceresini, 09/12/2013 09:58 AM
avviso_arrivo_merce_a.jrxml (33.1 KB) avviso_arrivo_merce_a.jrxml Jasper not working Luca Sceresini, 09/12/2013 09:58 AM
StyleTemplate1.jrtx (418 Bytes) StyleTemplate1.jrtx template file, which defines two styles Andrei Costache, 03/03/2014 09:30 PM
customers_svy52.jrxml (1.81 KB) customers_svy52.jrxml report file based on foundset (example_data/customers) Andrei Costache, 03/03/2014 09:30 PM

History

#2

Updated by Andrei Costache over 10 years ago

Hi,

Could you try using the latest version of the plugin (4.x) along with a newer version of Servoy (6.x or 7.x)?

Regards,
Andrei

#3

Updated by Luca Sceresini over 10 years ago

No Andrei, actually we can't move from 5.3 to 6.x or 7.x (so we can't use the latest version of the plugin).
Have you discovered something about bug that I described above?

Thanks, Luca

#4

Updated by Andrei Costache over 10 years ago

Hi Luca,

Not much updates yet, unfortunately, except what we have discussed. But it will be looked at deeper.

Regards,
Andrei

#5

Updated by Andrei Costache over 10 years ago

Hi Luca,

Just wanted to check if you are still experiencing this or not.
Also, for a short recap, I think you are already using styles as documented https://www.servoyforge.net/projects/servoy-jasperreports/wiki/Foundset_Based_Reports_Guidelines.

We will be looking into this in the following weeks.

Regards,
Andrei

#6

Updated by Andrei Costache about 10 years ago

  • Status changed from New to In Progress
  • Assignee set to Andrei Costache
#7

Updated by Andrei Costache about 10 years ago

Hi Luca,

I have tested and looked into the style functionality and this all works fine, from my side.
My testing scenario is Servoy 5.2.17 and the Jasper plugin version 3.3.2 (as available on site).
I have used the following functions: compileReport, runReport. I have exported to 'view', 'pdf' format. I have compiled the report with and without specifying compiled report file destination parameter.
I am uploading my own jrxml and jrtx (template) files, the ones I used to test. Please have a look. Also do note, these are just small tests, but which show how the styling functionality should work.
If you have any questions, please reopen the case providing feedback.

Hope this helps.

Regards,
Andrei

#8

Updated by Andrei Costache about 10 years ago

  • Status changed from In Progress to Resolved

Also available in: Atom PDF