Programmers all know the fact that in the process of developing a robust application, coding only costs about 20% of time, while debugging and optimization cost about 80%.
The same thing happens in web reporting application development. After designing and deploying, users often have to modify and release the web report again and again. As a result, report design and deployment cost 20% of total time, while debugging and optimizing according to users’ real requirements cost 80%.
Therefore, the speed of report debugging is very important.
Next, a skill which can increase RAQ Report debug speed will be introduced. With it, users can speed up the process of repeated modifying and publishing greatly.
Users of RAQ Report may meet this problem. After modifying a web report, and uploading it to web application server, users have to restart the server to update the report to new version. Otherwise, the report remains the same as old report before modifying.
Restarting the server everytime decreases the development efficiency greatly.
In theory, if users do not configure XML file again, there is no need to restart J2EE application server. Therefore, the problem may be caused by the cache of application server.
This time, RAQ Report also provides a wonderful method to solve the problem.
In development and testing phase, users can set RAQ Report server to update cache each time browsing report. After testing and debugging, users can set RAQ Report server to work with cache when launch the web report again.
The specific method is as follows:
When deploying the project, set the reportConfig.xml file in the release directory as follows:
Then, the web report can update promptly each time users upload new report. After development and testing, users can use the cache of J2EE application server again to enhance report performance by deleting this configuration.