Resolved/Known Issues in This Release

This document describes the resolved issues and any known issues for JReport in this release.

Resolved issues

Known issues

Summary field disappears from design view when deleting table column

If a summary is inserted in the GroupFooterPanel of a table, when you delete a column from the table, or unmerge the cell of the group footer row, sometimes you may find the summary field disappears from design view, however, from the report structure tree in the Report Inspector, you can still find the object. You can reset its coordinate related properties so as to make the summary field display again.

Compiling formulas in JReport under JDK 6 or higher gets warnings

Since generic type is introduced to JDK 6 or higher version, when compiling formulas in JReport under JDK 6 or higher, you may come across warning messages as follows:

• Note: Test.java uses unchecked or unsafe operations.
• Note: Recompile with -Xlint:unchecked for details.

You may see that the situations are logged as Javac errors. However, the warning messages do not prevent Javac from creating .class files and reports can still run correctly.

In this case, you can simply ignore the messages and logged errors.

TOC Browser tree doesn't work well for reports with cached report bursting

When end user runs a report which has been defined with some cached report bursting policy in Page Report Studio, and then opens the TOC Browser, he will see all the groups of the report instead of just the ones he is supposed to view. In addition, no matter if he has access to a group, he cannot click the group name from the TOC tree to get corresponding details. JReport will further enhance the cached report bursting feature in a future release to resolve this issue.

Report data gets cut off in PDF result

When you export a report to PDF format, if the report contains a large amount of data but its page mode was specified to be continuous page mode, or its page size was set to be larger than 200 inches, you will find that in the PDF result some data of the report are cut off. This is because in one PDF page, the data displayed can be no larger than 200 inches.

Starting JReport with 64-bit JDK 1.7

To use 64-bit JDK 1.7 to start JReport on 64-bit Sun Solaris System, you need to modify the launch script JReport.sh (for JReport Designer) or JRServer.sh (for JReport Server) in $REPORTHOME/bin by changing the value $JAVAHOME/bin/java to $JAVAHOME/bin/amd64/java.

Deploying monitor.war (servlet.war) and jreport.war in the same domain gets exception

When integrating JReport Server and JReport Server Monitor into one application server, you need to make sure that they are deployed to different domains. JReport Server Monitor is supposed to be just an application for the administrator which doesn't need to come along with a JReport Server as the report system. So it is recommended that JReport Server Monitor be installed on a separate system or on systems for system administrators.

Limitation of going to another group on chart

When you perform the go-to action on a chart which uses a dynamic formula as its shown value, and the formula contains group information, you will get exceptions. This is a limitation in current version. We will resolve the issue in future release.

The zooming in or out of JReport browsers is not supported

All JReport browsers such as Page Report Studio, Web Report Studio, JDashboard and so on do not support being zoomed in or out by the way of scrolling the mouse while holding the Ctrl key. This may result in that the JReport UI cannot display well.

Derby cannot auto start in cross-computer integration

By default, JReport Server uses the embedded Derby as the system database, and automatically starts the Derby database server (the start of Derby requires the JDK path). If you build a WAR/EAR on computer A and then integrate it into an application server on computer B, it is probable that the Derby database server cannot auto start using the JDK path on computer A. If you want to use Derby in an integration environment, please take the following steps:

1. Build a WAR(jreport.war)/EAR(jreport.ear) on computer A using the following commands:

   makewar.bat -Dreporthome=%REPORTHOME%

   makewar.bat buildEar -Dreporthome=%REPORTHOME%

2. Deploy jreport.war/jreport.ear to the application server on computer B.
3. In %ReportHome%\derby\bin, modify javahome in the env.bat file to make it the same as that of computer B.
4. Access the URL http://ip:port/jreport to start JReport Server, and Derby will also get started.

API change

jet.formula.ParamDesc.value has been set to private now. You can use getDisplayValue(DbValue paramvalue, java.util.Locale locale) instead.

For example:

ParamDesc desc = new ParamDesc();

... ...

desc.getDisplayValue(desc.getValue(), Locale.getDefault());