Fanruan 10 mobile terminal adaptation process record

background

Recently, the Fanruan report embedded in the project has been adapted on the mobile terminal and supports display on the mobile terminal. The version upgrade has been introduced in the previous period ( the version upgrade of Fanruan FineReport ). This issue mainly records the problems and solutions in the adaptation process.

exception handling
1. The request cannot find the js file

Problem description
When accessing in mobile phone mode, the js file will be loaded, and the request is shown in the figure below at F12 on the front end.
insert image description here
Solution
: The 404 not found files, mainly including the following files, can be found on the server deployed by Fanruanfr-plugin-toolbarfloat-10.4.999.jarCopy the decompressed com folder to the specified location.

/com/fr/plugin/mobile/web/dist/js/vendor.777b5.js
/com/fr/plugin/mobile/web/dist/js/app.02b63.js
/com/fr/web/core/js/van.utils.js
/com/fr/web/core/js/vancharts-all.js
/com/fr/web/core/css/leaflet.css
2. When the page loads, the network request fails

Description of the problem
In the mobile phone mode, the network request in the pop-up window fails, and the page display is abnormal.
Solution
Check the loading under F12 on the front end/decision/url/mobile/view/firstdatamethod, a redirection is made at the proxy layer of the project, and the page loads normally.

3. Pop-up window - node error

Problem Description
A node null pointer exception is reported after the page is refreshed.

出错节点ID: [ 593e4e30-80ba-1876-62d0-b1659cf78547 ]
java.lang.NullPointerException
	at com.fr.data.impl.MemCachedDBDataModel.getRowCount(MemCachedDBDataModel.java)
	at com.fr.data.index.AbstractIndexDataModel.getRowCount(AbstractIndexDataModel.java)
	at com.fr.data.impl.FormulaDisplayDictionary.createKVS(FormulaDisplayDictionary.java)
	at com.fr.data.impl.FormulaDisplayDictionary.get(FormulaDisplayDictionary.java)

Solution:
Search the logs under Tomcat, and find that the reason is the problem of SQL association conditions, lack of tables, and the data is normal after supplementing the relevant tables.

Guess you like

Origin blog.csdn.net/u012190388/article/details/131113333