# Resolved/Known Issues in This Release

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

## Resolved issues

Case Number | Bug ID | Issue
--- | --- | ---
[Jinfonet #45204] | 32450 | After JReport Designer was upgraded to V8, when user exports the report results to PDF format, some data using some fonts was cut off. Exporting to PDF now works with all fonts.
[Jinfonet #49229] | 34556 | The data type Clob is now supported in Oracle stored procedure UDS.
[Jinfonet #49229] | 35037 | When we bind parameters to Oracle UDS, if we set the value type of the parameter to be Number, JReport now uses a default length and scale for the value so that it will not throw an exception when the length and scare are not set by the user.
[Jinfonet #49488] | 32508 | JReport now supports calling the API String[] sqls = dr.getSQLs(); String[] sqlColumns = cat.getSQLColumns(sqls[0]) instead of throwing a java.lang.ClassCastException.
[Jinfonet #49806] | 32482 | JReport Queries now support the Configure Reference function.
[Jinfonet #49821] | 32541 | When user sets the option to repeat the group header in a banded object, if there is not enough space for the group header in the first page, it will be shown on the second page.
[Jinfonet #49831] | 32491 | You can now use OOJDBC to connect with XML data sources. This was not supported in previous versions.
[Jinfonet #49973] | 34331 | The embedded fonts in subreports can now be displayed in the whole report.
[Jinfonet #50125] | 32465 | The LONGVARCHAR field is now supported in JReport without truncation.
[Jinfonet #50216] | 32550 | When the user sets "Duser.language -Duser.country -Dfile.encoding=" in JReport.bat, the corresponding characters will now be displayed correctly.
[Jinfonet #50310] | 32638 | JReport Designer API now logs the detailed error information if user's inserting SQLQuery failed after upgrading from previous versions.
[Jinfonet #50406] | 33683, 33685 | When a crosstab is inserted into the group header panel of a banded report, if the crosstab contains more rows than fit on one page, the rows will be displayed on the next page.
[Jinfonet #50729] | 33542, 33761 | When parameters of a user defined data source are changed, the report cube based on the UDS now works correctly.
[Jinfonet #50760] | 34999 | The DSPage instances now use less memory when user exports the report to Excel.
[Jinfonet #51015] | 34681 | JReport now supports compiling formulas for XML based catalogs (.cat.xml) files.
[Jinfonet #51197] | 34790 | The box border now does not overlap the page footer and page header panels in PDF results.
[Jinfonet #51398] | 35340 | When exporting a report which has a subreport with the On New Sheet property enabled to Excel, the sheet name of the subreport now displays as specified by the Sheet Name property.
[Jinfonet #51509] | 35554 | Data of a subreport can be fully displayed in its main report now.

## Known issues

The installation is hung when installing JReport products with 64-bit JDK on Windows platform

You may need to install JReport products with a 32-Bit JDK and then switch to your preferred 64-bit JDK after installation. If there is only a 64-Bit JVM on your Windows platform, you need install a 32-Bit JDK and then install JReport products with the JDK using installation argument –is:javahome. For example, to install JReport Designer: `C:\>jrpsetup.exe –is:javahome C:\Applications\Java\jdk_32bit`. After installation, you can specify 64-bit JDK to run JReport products by set JAVAHOME environment variable. For example: `set JAVAHOME= C:\Applications\Java\jdk_64bit in setenv.bat under %JREPORT%\bin`.

Compiling formulas in JReport under JDK 1.5 or higher gets warnings

Since generic type is introduced to JDK 1.5 or higher version, when compiling formulas in JReport under JDK 1.5 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 the logged errors.

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.