Skip to main content

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.

Jump to: navigation, search

Difference between revisions of "Ecore ODA Driver-Proposal"

Line 15: Line 15:
 
The Ecore ODA Driver is only available from [[#CVS|CVS]]. After checking the code out a number of dependencies may be un-met in your workspace such as: [[Connectivity|Datatools Connectivity]], [http://www.eclipse.org/modeling/emft/?project=search#search EMF Search], [http://www.eclipse.org/modeling/emf/?project=transaction#transaction EMF Transaction], and [http://www.eclipse.org/modeling/emf/?project=query#query EMF Query].  You will also need to install the EMF Model Query OCL Integration feature (or the "Next" button on the New Data Source Wizard for the Ecore ODA Data Source will be disabled) and the Data Tools Platform Enablement for JDBC (or you will see assertion failures in the ConnectionProfileManager for a missing generic db JDBC profile).
 
The Ecore ODA Driver is only available from [[#CVS|CVS]]. After checking the code out a number of dependencies may be un-met in your workspace such as: [[Connectivity|Datatools Connectivity]], [http://www.eclipse.org/modeling/emft/?project=search#search EMF Search], [http://www.eclipse.org/modeling/emf/?project=transaction#transaction EMF Transaction], and [http://www.eclipse.org/modeling/emf/?project=query#query EMF Query].  You will also need to install the EMF Model Query OCL Integration feature (or the "Next" button on the New Data Source Wizard for the Ecore ODA Data Source will be disabled) and the Data Tools Platform Enablement for JDBC (or you will see assertion failures in the ConnectionProfileManager for a missing generic db JDBC profile).
  
Once these dependencies have been met, you can run the BIRT Report Designer (after you have installed [http://www.eclipse.org/birt/phoenix/ BIRT], of course) and create a new report.  You might want to use the sample [http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.emf/org.eclipse.emf/tests/org.eclipse.emf.test.tools/data/ant.expected/models/1.4/creation/library.xsds/emf/library.ecore?root=Modeling_Project&view=co library.ecore] and [http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.emf/org.eclipse.emf/tests/org.eclipse.emf.test.tools/data/ant.expected/models/1.4/creation/library.xsds/emf/elements.ecore?root=Modeling_Project&view=co elements.ecore] to get started.  When adding a Data Source, a new type will display <tt>Ecore ODA Data Source</tt> and the wizard will allow you to choose an ecore file.  Selecting and naming this Data Source and giving the name of an ecore file will allow you to enter a new Data Set.  This is, however, pretty much the end of the line. As explained in [[#Status|Status]], above, the code is not yet complete. Column selection has not been implemented and the code currently in CVS does not correctly persist preferences.
+
Once these dependencies have been met, you can run the BIRT Report Designer (after you have installed [http://www.eclipse.org/birt/phoenix/ BIRT], of course) and create a new report.  You might want to install the [http://www.eclipse.org/modeling/emf/updates EMF 2.3.2 Examples] and create an instance of an .extlibrary file to get started.  When adding a Data Source, a new type will display <tt>Ecore ODA Data Source</tt> and the wizard will allow you to choose a file.  Selecting and naming this Data Source and giving the name of a file will allow you to enter a new Data Set.  This is, however, pretty much the end of the line. As explained in [[#Status|Status]], above, the code is not yet complete. Column selection has not been implemented and the code currently in CVS does not correctly persist preferences.
  
 
== Contributors ==
 
== Contributors ==

Revision as of 14:03, 3 April 2008

Introduction

The Ecore ODA Driver is a proposed component of the DTP Incubator project. It will provide the ability to query Ecore models using OCL by implementing the Open Data Access (ODA) API. The restriction to use OCL (text-based) queries is based on the design of the ODA API. EMF Queries may be supported at runtime in the future.

Status

Initial code has been committed (see CVS, below) but the code is not yet complete. While most of the driver itself is in place the UI requires some finish work.

Contribution tracked at Bugzilla 132958.

It is hoped that a useful release will be complete in time for Ganymede.

Getting Started

The Ecore ODA Driver is only available from CVS. After checking the code out a number of dependencies may be un-met in your workspace such as: Datatools Connectivity, EMF Search, EMF Transaction, and EMF Query. You will also need to install the EMF Model Query OCL Integration feature (or the "Next" button on the New Data Source Wizard for the Ecore ODA Data Source will be disabled) and the Data Tools Platform Enablement for JDBC (or you will see assertion failures in the ConnectionProfileManager for a missing generic db JDBC profile).

Once these dependencies have been met, you can run the BIRT Report Designer (after you have installed BIRT, of course) and create a new report. You might want to install the EMF 2.3.2 Examples and create an instance of an .extlibrary file to get started. When adding a Data Source, a new type will display Ecore ODA Data Source and the wizard will allow you to choose a file. Selecting and naming this Data Source and giving the name of a file will allow you to enter a new Data Set. This is, however, pretty much the end of the line. As explained in Status, above, the code is not yet complete. Column selection has not been implemented and the code currently in CVS does not correctly persist preferences.

Contributors

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

Back to the top