Overview
Version
Report Server Version | Functional Change |
11.0 | / |
11.0.20 | Optimized the plugin overwriting logic. When a plugin is synchronized from the server to the designer, other versions of the plugin are automatically cleared. |
Problem
Version mismatch between JAR packages and plugins is mainly divided into three types:
1. Version mismatch of JAR packages between the local designer and the remote server project when you design remotely
2. Plugin version mismatch or plugin mismatch between the local designer and the remote server project when you design remotely
3. Version mismatch between manually installed plugins and JAR packages of the designer/server
This document mainly explains problems caused by these mismatches and corresponding solutions.
Version Mismatch Between JAR Packages and Plugins in Remote Design
When you remotely design and connect to the server through the designer, versions of JAR packages and plugins of the designer and the server need to be consistent. Otherwise, a series of problems may occur during the design.
Problem
During the remote connection from the designer to the server, if there are mismatches between JAR packages and plugins of the server and the designer, a prompt occurs in the notification center in the top right corner of the designer, indicating that The remote design environment is different, which may affect some functions.
Solution
Click Sync to Local.
1. Overwrite the local designer JAR package with the server JAR package that differs.
2. Install the plugins that are enabled on the server but not installed locally into the local designer.
3. Overwrite the local designer plugins with the plugins that differ and are already enabled on the server. In FineReport V11.0.20 and later versions, other versions of local plugins are deleted automatically.
After completion, the designer is automatically restarted and remotely connected to the server again.
1. If some plugins fail to synchronize, there may be two reasons: This plugin has been removed from the plugin store for some reason. This plugin is built-in and does not require manual installation. You can simply restart the designer. 2. If the designer is in an intranet environment: You need to manually upgrade the designer. You need to manually copy all plugin packages under the path %Tomcat_HOME%/webapps/webroot/WEB-INF/plugins of the server and paste them under the path %FR_HOME%/webapps/webroot/WEB-INF/plugins and %FR_HOME%/plugins of the designer. After completion, restart the designer.Note:
Problems Caused by Mismatched JAR Packages Versions
Preview effects of some templates mounted on the platform are different from those on the local.
Chart elements are displayed incompletely, such as incomplete chart percentages and absent extended charts.
Fail to preview templates and datasets with errors.
Fail to switch working directories.
Template content is displayed incompletely. For example, datasets in templates and some widgets are absent.
Table data in databases cannot be matched despite a successful data connection.
You have no permissions when renaming or saving templates.
The following introduces some problems in detail.
Fail to Preview Despite a Successful Data Connection
When you create new datasets, views and tables are not displayed though the data connection is successful. A prompt pops up, indicating that the database connection failed.
An error occurs in logs: connection pool shut down.
Error in Dataset Preview
An error occurs when you preview datasets, indicating that java.lang.reflect.UndeclaredThrowableException.
No Permissions for Template Operations
When you rename or save templates during the remote design, a prompt occurs, indicating that you have no permissions.
Warning During Remote Connection
When you switch the working directory to the remote server, a warning pops up, indicating that Remote design can be connected, but the versions do not match.
Unavailable Fetchsize Function on the Platform
The Fetchsize function under Data Connection > Data Connection Management may be unavailable.
Mismatched Versions Between Plugins and JAR Packages
The JAR package version requirements of each plugin can be found on the plugin management page, the FanRuan market plugin page, and in the corresponding plugin document.
Version mismatch between plugins and JAR packages affects the use of plugins (and even the running of the whole project). Therefore, you are advised to ensure that their versions match with each other.
After you install or update plugins/projects, version mismatches may occur, posing hidden risks to the project if there is no warning or restriction. For JAR packages 2021/01/25 and later versions, plugins are automatically disabled if JAR packages of the project do not match plugin versions. You are notified at the same time.
The system automatically detects whether the versions of plugins and JAR packages match when you install, update, upgrade, and enable plugins, or start the project after upgrade in Plugin Management. A prompt occurs if the versions do not match.
The system detects whether major versions match with each other (for example, whether there are situations of V10.0 matching V11.0) and whether the JAR package version of the current project is suitable for the minimum JAR package version required in the plugin instructions.
Problem in Plugin Configuration
Problem:
If plugin versions match JAR packages when you install (online/locally), update, or enable plugins, you can perform normal operations. A prompt occurs, indicating that the operation is successful. If plugin versions do not match JAR packages, the installation fails with a pop-up prompt, indicating that versions do not match with each other.
If plugin versions are higher than that required by the JAR package, a prompt pops up: XXX has a too high version. Upgrade the JAR package or install the plugin of an earlier version.
If plugin versions are lower than that required by the JAR package, a prompt pops up: XXX has a too low version. Install the plugin of a higher version.
Solution: You need to check the versions of the installed plugin and the JAR package, and adjust them to be consistent.
For details about deleting/upgrading server plugins, see Server Plugin Management.
For details about deleting/upgrading designer plugins, see Designer Plugin Management.
Problem in Project Startup
Problem:
After update, if the plugin versions do not match that required by the JAR package when you start the project, the plugin will be disabled. A prompt pops up when the admin logs in to the platform.
Note:If plugin versions are higher than that required by the JAR package, a prompt pops up: XXX has a too high version. Upgrade the JAR package or install the plugin of an earlier version.
If plugin versions are lower than that required by the JAR package, a prompt pops up: XXX has a too low version. Install the plugin of a higher version.
Solution: Click the message to jump to the Plugin Management page. You can also go to System Message on the platform and click Process to redirect to the Plugin Management page, where the admin can delete or update plugins.
For details about deleting/upgrading server plugins, see Server Plugin Management.
For details about deleting/upgrading designer plugins, see Designer Plugin Management.
Problem in Designer Use
Problem:
If plugin versions do not match the local designer JAR package versions, a pop-up window appears when you start the designer, indicating that The following plugins do not match the JAR package version and have been disabled.
The pop-up window provides a detailed list of incompatible plugins. Click Process Immediately to redirect to the Plugin Management page.
When you switch to other local directories in the designer, the system also checks whether plugin versions match JAR package versions. If not, a pop-up window appears.
Note:
Solution: Click Process Immediately to delete or update plugins.
For details about deleting/upgrading server plugins, see Server Plugin Management.
For details about deleting/upgrading designer plugins, see Designer Plugin Management.
