Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Ecore ODA Driver"
| Line 14: | Line 14: | ||
Recently, a backport of these plug-ins was checked-in to CVS for use with Eclipse 3.2, EMF 2.2 and JDK 1.4. The backport has no guarantee of future support. If you would like instructions for using these versions of the plug-ins, please look [http://timezra.blogspot.com/2008/05/oda-ecore-driver-backport.html here]. | Recently, a backport of these plug-ins was checked-in to CVS for use with Eclipse 3.2, EMF 2.2 and JDK 1.4. The backport has no guarantee of future support. If you would like instructions for using these versions of the plug-ins, please look [http://timezra.blogspot.com/2008/05/oda-ecore-driver-backport.html here]. | ||
| + | |||
| + | == Connection Properties and Profiles == | ||
| + | |||
| + | In order to support requests for [https://bugs.eclipse.org/bugs/show_bug.cgi?id=243099 Connection Profiles] and [https://bugs.eclipse.org/bugs/show_bug.cgi?id=243499 Connection Properties], we made some changes as of August 22, 2008 that will affect existing reports, i.e., the Model file location is now stored directly as a URI, the property for this URI has been renamed, Column Selections are contained in a single property (instead of in properties with increasing numbers), and the name of the Column Selection property has been changed. Hopefully these fixes will not be too disruptive to existing reports and the benefit of dynamic property binding will outweigh the inconvenience of either manually editing existing reports or re-creating those reports. | ||
== Installation == | == Installation == | ||
Revision as of 10:27, 22 August 2008
Contents
Introduction
The Ecore ODA Driver was created to allow an EMF ECore model to serve as an ODA data source. This makes it simple for BIRT reports to draw data from Ecore models.
This component has been proposed to the new DTP Incubator. It is hoped (perhaps optimistically) that it can join in the Ganymede release in June of 2008.
Tutorial
Tim has written a tutorial for the Ecore ODA Driver at Overcoming Fear.
Below you'll find some of the same information but without the detail or pretty pictures.
Backport to Eclipse 3.2, EMF 2.2 and JDK 1.4
Recently, a backport of these plug-ins was checked-in to CVS for use with Eclipse 3.2, EMF 2.2 and JDK 1.4. The backport has no guarantee of future support. If you would like instructions for using these versions of the plug-ins, please look here.
Connection Properties and Profiles
In order to support requests for Connection Profiles and Connection Properties, we made some changes as of August 22, 2008 that will affect existing reports, i.e., the Model file location is now stored directly as a URI, the property for this URI has been renamed, Column Selections are contained in a single property (instead of in properties with increasing numbers), and the name of the Column Selection property has been changed. Hopefully these fixes will not be too disruptive to existing reports and the benefit of dynamic property binding will outweigh the inconvenience of either manually editing existing reports or re-creating those reports.
Installation
The Ecore ODA Driver is currently only available from CVS. After obtaining the code, you may notice the driver has a number of dependencies that are un-met in your workspace:
| Dependency | Update Site | Path |
|---|---|---|
| BIRT Report Designer | http://download.eclipse.org/releases/ganymede/ | Charting and Reporting/Eclipse BIRT Report Designer Framework |
| Datatools Connectivity | http://download.eclipse.org/releases/ganymede/ | Enabling Features/Data Tools Platform Connectivity |
| Data Tools Platform Enablement for JDBC | http://download.eclipse.org/releases/ganymede/ | Enabling Features/Data Tools Platform Enablement for JDBC |
| EMF Query | http://download.eclipse.org/releases/ganymede/ | Enabling Features/EMF Model Query |
| EMF Model Query OCL Integration | http://download.eclipse.org/releases/ganymede/ | Enabling Features/EMF Model Query OCL Integration |
| EMF Transaction | http://download.eclipse.org/releases/ganymede/ | Enabling Features/EMF Model Transaction |
Using the Driver
Those less familiar with EMF or without a handy EMF model should install the EMF Examples from http://www.eclipse.org/modeling/emf/updates and create an instance of an .extlibrary file with some data. It's outside the scope of this document to describe this process, but typical readers will already have familiarity with EMF editors.
Of course, any serialized EMF model will do, as long as the package has been registered so that the Java classes representing the model are available at runtime.
Create a Report
The primary consumer of ODA data sources is BIRT. Typically, creating a BIRT report is the first step to using the Ecore ODA Driver.
Create an Ecore ODA Data Source
Any ODA drivers registered with the platform show up within BIRT as data source types, each with a wizard to allow for the entry of connection information. In the case of the Ecore ODA Driver, the only information required by the connection is the path to a serialized Ecore model of a registered model type. (If you aren't familiar with registering EMF models, see this question in the EMF/FAQ.) Attempting to load a serialized model for an unregistered package will result in an error.
Create an Ecore ODA Data Set
Once a data source has been created for your Ecore model, use the New Data Set wizard to launch the Ecore ODA Data Set Wizard.
...to be continued... Feature changes in process--screen shots forthcoming...
CVS
The Ecore ODA Driver and UI can be checked out of CVS from the Datatools_Project Repository of dev.eclipse.org with a path of org.eclipse.datatools.incubator/plugins.
Browse: ViewCVS