Comparison of main java report tools

From the deployment, presentation, design and other aspects, a comprehensive comparison of Java reporting tools, such as reporting tool leader href = "http://www.runqian.com.cn/rqrpt/rqwebreport.htm" target = _ blank> runqian, Jie table, style report, jasper, and Crystal Reports that claim to support Java.

Java report tools can be divided into two categories: pure Java report tools and "supported" Java report tools.

"Supported" Java reporting tools:

The reporting tool that supports Java is actually a non-Java reporting tool, but it can be used in JavaProgram. There are many such products. In general, one category is independent report servers, such as Bo/crystal report, Brio, Cognos, and Qin. The other category is composed of controls on the front end, such as massive reports.

The problem with the independent Report Server is:

An independent Report Server directly limits the performance bottleneck of reports.
The cluster capability of the Web server cannot be shared.
Unable to share the web server's connection pool management capability
Uniform deployment is not possible. implementers must deploy their own web applications and report servers.
An independent Report Server often has its own user role management mechanism, which is frequently associated with user applications.
> ReferenceArticle: Services without servers

The front-end control method has the following problems:

It is very troublesome for users to deploy, and controls must be installed on each machine. (To solve this problem, some vendors move the report calculation work of the original control to the server, but it can only run in Windows because it is not pure Java)
The control produces performance problems for large reports, because the report generation and calculation work are implemented in the control.
The application system cannot flexibly control the report through APIS-because it is in the control.
Product upgrade-it will be a major problem, and the client must re-download the new control.
This comparison does not mean that other methods cannot be used, but it is clear that for reports in the Java environment, pure Java report products should have inherent advantages. In fact, this point does not need to be discussed. In the past, there were still a batch of control-based products that were barely used by the products of independent servers, the reason is that the pure Java-based report product did not appear yet. If there is a suitable Java platform product (the premise is to be easy to use), of course, it is a pure Java product.

Pure Java report tool

Java-only reporting tools mainly include:

report tool leader href = "http://www.runqian.com.cn/rqrpt/rqwebreport.htm" target = _ blank> runqian is a very powerful Web Report product, excellent in all aspects, in particular, its new generation report model uses revolutionary technologies such as multi-source sharding, irregular grouping, dynamic inter-grid operations, and row-column symmetry, it can easily complete many complex or even difficult-to-implement reports from traditional report tools. Initially, rundry was concentrated in the high-end market, but now it has begun to adopt a more comprehensive market strategy to provide multiple versions across the board, providing comprehensive choices for users with different needs. Runqian's problem is that there is no piracy available currently.
style report has an effect because it is a famous java report abroad. From the deployment perspective, it should be said that it also has the common characteristics of Java reports and is easy to deploy and integrate. It also supports HTML display and can be exported to PDF, Excel, etc. (however, it exports to excel to find the finest granularity of those rectangle boxes, and then use the merged lattice, A lot of cells will be created, and it is very difficult to use this file for subsequent operations ). However, in terms of design, it is only a traditional method. In the face of many complicated reports, the workload will be huge, and some may even be very difficult.
open-source products, such as Jasper and quasi-open-source products (only designers are sold and servers are free of charge ). The functions of these products are much weaker. Open source is not supported. Of course there are many discussion areas, but this is incomparable with the commercial support of reliable vendors. Although quasi-open source supports a little better, the limited revenue is not good for its long-term support and Product improvement, and it is a long-term risk for users.
compared with the above products, runqian is superior in all aspects, and its design advantages are even more prominent. Open-source or quasi-open-source products have their cost advantages (if you do not consider the cost ). As for style report, it seems that there is actually no advantage, right?