This document describes the resolved issues and any known issues for JReport in this release.
|
Item
|
Case #
|
Issue
|
|---|---|---|
|
1
|
61773 | NLS now works normally after user exports the report running with French Locale to a DHTML result file (RSD file). |
|
2
|
61795 | Now the Merge dialog works normally in merging catalogs. |
|
3
|
61864 | The catalog versions now display correctly in the Resources panel of the Administration page after user restores the catalog. |
|
4
|
62005 | Parameter values can now be saved in dashboards. |
|
5
|
62063 | Now when user exports a page report to Excel, the default options setting in the Export dialog uses the defaults the user saves in Profile > Customize Server Preferences >Export Formats tab. |
|
6
|
62118 | Users can now save report templates and results with file names containing non-English characters when using JReport Server in Tomcat or other application servers. |
|
7
|
62127 | Changed the default value of properties Horizontal Auto Size and Vertical Auto Size to true so that the DBField in a tabular report can include larger values. |
|
8
|
62194 | Supports setting the JNDI name via URL/API when scheduling or running page reports, web reports, and dashboards. |
|
9
|
62214 | Now when user removes a table in the query filter, the columns in other tables no longer change to unchecked. |
|
10
|
62214 | Solved the dead loop in BV resources which was caused by the cross reference and would lead JReport Designer to crash. |
|
11
|
62245 | Resolved the inconsistency in data after user did go-to-detail actions in a web crosstab report. |
|
12
|
62246 | All data formats can be changed now after you reset the Hint Value Format property of a pie chart. |
|
13
|
62299 | Non-constant value formulas now works well in getting value from the where clause. |
|
14
|
62300 | The calculation result in JReport Designer no longer is incorrect after user shifts to view the second page of a report. |
|
15
|
62302 | Resolved the labels cut-off issue when user sets the labels of the chart X axis to be displayed at an angle. |
|
16
|
62334 | Solved the failure in object layout when there is a subreport in the page header panel of a banded report and the main report is set as page layout. |
|
17
|
62344 | Labels in the DHTML report now can not be edited under basic view mode. |
|
18
|
62350 | Corrected the expression errors like "2st", "3st", and "4st" on the date parameter template. |
|
19
|
62370 | The decimal part of the average summary value no longer gets lost after user sets it to calculate and display with 2 decimal places. |
|
20
|
62372 | Cascading parameters now work normally on JReport Server after user changes the input language to Spanish(Bolivia). |
|
21
|
62427 | The images no longer get cut off in the JReport Viewer page when resolution is not set to the default value. |
|
22
|
62436 | Running reports created in JReport V7 version on JReport Server V11 no longer get exceptions. |
|
23
|
62448 | Now the Total line of the group in user's web table report can be displayed normally when it happens to be at the page break. |
|
24
|
62537 | All hint messages of the combo chart can now be displayed normally in JReport Studio. |
|
25
|
62538 | JReport now can always get the aliases of columns instead of the original field names when user has used alias names for SQL stored procedure. |
|
26
|
62569 | Components in dashboard no longer get shrunk on auto refresh. |
|
27
|
62569 | Nodes of the web chart report are now displayed normally in Firefox or Google Chrome. |
|
28
|
62569 | Tick marks in the web chart report no longer get overlapped in case there are lots of nodes on the graph. |
|
29
|
62569 | The web report toolbar is displayed normally now after the report is loaded in Internet Explorer. |
|
30
|
62585 | Fixed the "out of range" error which happens when user changes the value of a cascading parameter in a DHTML report. |
|
31
|
62696 | The user defined DateTime parameter now can be displayed normally in JReport Server when the locale in IE is something other than en-US. |
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:
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 JReport Viewer, if he opens the TOC Browser, he will see all the groups the report has instead of just the ones he is supposed to view. In addition, no matter if 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 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.
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, you should update dbconfig.xml when building the WAR/EAR, and remove the following line from dbconfig.xml:
<auto-start-derbyservice>true</auto-start-derbyservice>
Then JReport will not try to auto start the embedded Derby server, and you need to start it by yourself. Derby can be started and stopped by using the batch files in <install_root>/derby/bin. There you will find startNetworkServer.bat/sh and stopNetworkServer.bat/sh.
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 an 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.
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());