mchisty
-
Posts
13 -
Joined
-
Last visited
Content Type
Forum
Downloads
Featured Visualizations
Knowledge Base
Documentation (PDF Downloads)
Blog
Documentation (Test Area)
Documentation
Dr. Jaspersoft Webinar Series
Security Advisories
Events
Profiles
Entry Comments posted by mchisty
-
-
The video is nice. Also some detailed steps are provided. However, this may not be enough as JasperSoft Studio is highly buggy tool (not as robust as the older tool iReport); therefore the tutorial still may not work sometimes.
E.G.
Step 1: Once jar is created, we may need to add the jars under the "..apache-tomcatwebappsjasperserver-proWEB-INFlib" directory.
Step 2: If scriplet value shows in JasperStudio preview but the report output is not shown in JasperServer, this means there is a bug in 'DETAIL' band. I.E. if you place you scriptler inside 'Detail' band and preview it within Jaspersoft Studio, it will work just fine. Then publish it in Jasper Server and try to view the report, it will come as empty. This is bug in latest versions of Jaspersoft studio or, Jasper server (not sure which one, but all the TIBCO tools are buggy enough and not well documented. We need to find out resolution through lots of trial and error basis. TIBCO support team is not responsive at all)
To solve this, place the scriptler in any other band e.g. in the 'Summary' band, then preview it and it will work; then publish and view it in Jasperserver, this will also work.
-
Fine but there is one important point missing here:
The example provided here is applicable only if the report is in the same workstation with java appcation (the jasper report file .jrxml/.jasper is bundled with the web application, deployed in the same web/app server). But what if the report is depoyed in a remote jasper report server and not in the same server with the bundled web app? How do you pass the ArrayList of beans to the jasper file in such a case?
Thanks.
How to use URL query string parameters within your query-based input control
in How-To
Posted
This is a stupid article. Everyone who has basic Jasper knowledge can do this.
Here is a challenge for you: how can you resolve the issue if the URL has path variable instead of request parameter? I.E. if the URL is like this format,
- http://host:port/v1/clients/{clientId}/summary
(An example could be this: http://localhost:8080/v1/clients/189728/summary )
How can you solve this?