This way you can
get the best of both worlds. You would have the impressive set of features that WTP
offers, such as web service creation wizards, server deployments, and the ability to
debug applications in Eclipse. You would also be able to have the WYSIWYG report
editor of BIRT, for rapid development of data-driven user-facing interactivity.
This also allows users to develop Java applications that leverage the BIRT Report
Engine and quickly switch over to the Report Designer; so you can have you entire
development process under one roof. Plus, you can get the added bonus of utilizing
Eclipse's internal tools for team project management, such as the CVS tool, or using
the free Sub-eclipse third-party plug-in for Subversion repositories.
Currently, BIRT already leverages ODA for data extensibility; so this is one example
of how building on top of the Eclipse framework has benefited the BIRT project. By
utilizing the Eclipse Data Tools Project, BIRT can leverage the already existing driver
framework and not have to repeat the development cycle. Future plans include
integrating with WTP and other Eclipse projects as well.
Introduction
[ 16 ]
BIRT Distributions
As it stands right now, the BIRT Report Designer comes in two flavors: The
distribution I will be discussing in this book is the Eclipse BIRT, available at
http://www.
Pages:
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41