MyEclipse reports and Eclipse Birt detailed comparative analysis (bottom)

In the detailed comparative analysis of MyEclipse reports and Eclipse Birt (above), the small section introduces reports users of MyEclipse Birt, MyEclipse reports scope, project type, user interface weaving, etc. The next small series to continue to introduce other sections of the content, I hope to help everyone.

5. Support for JDBC driver data sources

The MyEclipse report can be applied directly to the MyEclipse JDBC driver as a report data source. The Data Explorer view has a new DataSource wizard, which also includes the MyEclipse JDBC driver option. During the report Web project creation and configuration phase, MyEclipse reports installs a specific myeclipse jdbc ODA driver to correspond to the MyEclipse JDBC data source. This ODA driver enables the Birt report engine to recognize the MyEclipse JDBC data source at run time.

Select a data source5.1 DTP JDBC Connection configuration file not supported

MyEclipse Database Explorer provides long-term functionality for the Eclipse DTP Project Super Collection. Therefore, DTP functionality is not directly supported in MyEclipse. For this reason, the MyEclipse report does not support Birt DTP JDBC data sources.

6. Derby Database Server and sample report

An integrated MyEclipse server sandbox is included with the MyEclipse. This sandbox includes an integrated Tomcat Web server, a derby database server, such as a schema and a preconfigured myeclipse Derby JDBC driver. The MyEclipse also incorporates online resources called sample on demand. The site provides a one-click installation of the MyEclipse project to demonstrate how to use popular Java EE and related technologies and frameworks. These sample projects are designed to run on the MyEclipse integration Server 0 configuration. Sample on-demand hosted sample MyEclipse Report project can be installed, deployed, and run by double-click.

Server view shows integrated Derby and Tomcat Server MyEclipse sample on Demand6.1 Birt Derby databases and sample reports are not supported

MyEclipse reports's infrastructure and demonstration sample mechanisms support MyEclipse Integration Server and sample on-demand. Therefore, the MyEclipse reports does not support Birt embedded Derby servers and sample reports.

7. Porting guidelines for Wtp-birt Web projects

The following procedure is used to create a MyEclipse report Web project, which is equivalent to the outline of a Wtp-birt Web project. Before you begin, you should be familiar with creating MyEclipse report Web projects and setting up MyEclipse JDBC Base driver data sources.

1. Create a myeclipse report Web project.
2. Copy the Java src folder and Web content resources from the Wtp-birt project to their location in the MyEclipse project where they are located. Do not copy the report engine.
3. For any report copied to the MyEclipse project, its data is a DTP JDBC data source, you need to replace the DTP JDBC data source with the MyEclipse JDBC data source, so you need to create a myeclipse JDBC driver and data source. Then replace each DTP JDBC data source in the data source of the MyEclipse project.
4. Testing in Report Designer uses preview mode to ensure that the dataset is working correctly, and to correct each error in the report for you.

8. MyEclipse Reports Installation Guide

MyEclipse reports is implemented using the Birt framework, but this does not mean that MyEclipse reports and Birt can be installed in the same myeclipse environment. When they are installed in the same myeclipse environment, their plug-ins can cause serious conflicts that do not work properly. Therefore, you can only install one product in a myeclipse environment.

If your MyEclipse installation does not include MyEclipse Reports, you can install this feature by selecting Help>choose components from the menu.

MyEclipse reports and Eclipse Birt detailed comparative analysis (bottom)