This document describes the resolved issues and any known issues for JReport Enterprise Server in this release.
|
Case Number
|
Bug ID
|
Issue
|
|---|---|---|
| [Jinfonet #48601] | 33558 | JReport Enterprise Server can be stopped on Tomcat now. |
| [Jinfonet #49229] | 33384 | Users are now able to establish more than 20 connections with URL in a JReport connection pool. |
| [Jinfonet #49229] | 34542 | In an RMI integration environment, the last modified time can now be displayed on the JReport Enterprise Server pages even if the RMI environment and the standalone server are not in the same machine. |
| [Jinfonet #49229] | 34543 | The Set Fetch Size property in JdbcDriversConfig.properties works well on JReport Enterprise Server now. |
| [Jinfonet #49229] | 34545 | Support information is now caught for user connection to optimize performance. |
| [Jinfonet #49229] | 34548 | Correct exception is thrown out when the Server API tries to get a user that hasn't an existing user name. |
| [Jinfonet #49229] | 34552 | When using banded column parameter in a report, user does not need to remove the additional SQL statement for each calling getParam() now. |
| [Jinfonet #49229] | 34555 | The logic of validation connection has been changed to optimize performance. |
| [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 #49655] | 32246 | Parameters provided in the DHTML tag library are now sufficient enough to run a report set, such as jrs.auth_uid, jrs.auth_pwd, jrs.authentication. |
| [Jinfonet #49799] | 32439 | When user sets server.rmi.host to be the virtual IP address in server.properties, he can use RMI services well now. |
| [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 #49869] | 32313 | Catalogs published from real paths can also be used as linked catalog to run reports. |
| [Jinfonet #49973] | 34331 | The embedded fonts in subreports can now be displayed in the whole report. |
| [Jinfonet #49977] | 34254, 34255 | When a report with summary is exported to Excel and the format is selected to be Preserve Report Formatting, the result is correct now. |
| [Jinfonet #50112] | 32430 | Users can set pwd=null in a catalog connection now. |
| [Jinfonet #50188] | 32648 | Reports run well on JReport Enterprise Server that is upgraded from previous version to V8.2. |
| [Jinfonet #50216] | 32550 | When the user sets "Duser.language -Duser.country -Dfile.encoding=" in JREntServer.bat, the corresponding characters will now be displayed correctly. |
| [Jinfonet #50310] | 32660 | The new feature of using scroll wheel to go to the next page in DHTML now has its option setting in the DHTML Preference page. |
| [Jinfonet #50310] | 34270 | When user clicks the Sort button on the DHTML toolbar to sort the report, even with the instance name of a component in the report contains space, he no longer gets the JRSInvalidParameterException. |
| [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 #50427] | 32835 | If user runs DHTML report by a very long URL, he will no longer get exception when creating .param file in RMI integration environment. |
| [Jinfonet #50458] | 33065 | The SQL exception is displayed on DHTML error information page now. |
| [Jinfonet #50477] | 33296 | The logic of the current parse parameter value has been modified more canonical. |
| [Jinfonet #50480] | 33559 | If user calls HttpUtil.checkAdminLogin(request, response) and the parameter is non serializable, he no longer gets Non Serializable attribute exception. |
| [Jinfonet #50552] | 33107 | When user runs a DHTML report by URL, the URL is now correctly displayed and the report can work perfectly well. |
| [Jinfonet #50555] | 33071 | Ad hoc reports can be saved to any folder other than where the catalog it uses locates and run well from the saved folder. |
| [Jinfonet #50555] | 35071 | When saving an ad hoc report with the same name as an existing report, the linked catalog now is updated based on the actual catalog the newly saved report uses. |
| [Jinfonet #50606] | 34264 | User can cancel the search operation on a DHTML report as desired. |
| [Jinfonet #50717] | 35550 | Although the user's key does not support ad hoc feature, but he still can move components in DHTML report in V8.2. |
| [Jinfonet #50719] | 35042 | When an ad hoc report applies a business filter which contains parameters, end users now will be asked to specify the parameter values each time he runs the report. |
| [Jinfonet #50732] | 33585 | When using the IN operator to set filter condition on a DHTML report, if user chooses to type in the values manually separated by ",", the filter condition can now be successfully applied to the report. |
| [Jinfonet #50760] | 34999 | The DSPage instances now use less memory when user exports the report to Excel. |
| [Jinfonet #50894] | 35296 | Now the accurate error message is shown in the Error Message column of the completed table and in JReport Enterprise Server log file. |
| [Jinfonet #50899] | 34537 | Much shorter time is now required to open the Search dialog when a report contains a large amount of data. |
| [Jinfonet #51197] | 34790 | The box border now does not overlap the page footer and page header panels in PDF results. |
| [Jinfonet #51216] | 34818 | In RMI environment, if user selects the Single File option when he schedules an HTML report to version, he is now able to visit the HTML result file via URL. |
| [Jinfonet #51238] | 34949 | The True Type Font (TTF) can get bold in HTML and DHTML results. |
| [Jinfonet #51250] | 35254 | When users print labels in Margin or Landscape format, they can get the expected exporting result. |
| [Jinfonet #51260] | 35310 | Users can now change the database connection information for business cubes at report runtime. |
| [Jinfonet #51347] | 35204 | While accessing JReport Enterprise Server from JReport Viewer Bean and calling zoom to view report, the report now displays well. |
| [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 displays as specified by the Sheet Name property now. |
| [Jinfonet #51322] | 35342 | Two subreports that are inserted side by side in the banded footer panel and returning different values from the database can now show their own data after the main report is published to JReport Enterprise Server. |
| [Jinfonet #51387] | 35366 | When using the datasource.xml file to redirect the connection to a JNDI connection pool defined by the web server, reports can run with the new connection well in JReport Enterprise Server now. |
| [Jinfonet #51405] | 32445 | JReport can now release the left-off connections well. |
| [Jinfonet #51509] | 35554 | Data of a subreport can be fully displayed in its main report now. |
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:
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 Page-level Security
When end user runs a report which has been defined with some page-level security policy in JReport Web, if he opens the TOC Browser, he will be displayed with all the groups the report has instead of the ones he is supposed to view. In addition, no matter a group is allowed for him or not, he cannot click the group name from the TOC tree to get corresponding details. JReport will further enhance the Page-level Security feature in future release to resolve this issue.