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 "Use Case - Create a Custom ODA Data Source"

m (Added page title)
m (UC CONN ODA Create Custom ODA Provider moved to Use Case - Create a Custom ODA Data Source)
(No difference)

Revision as of 22:57, 17 October 2006

Creating a Custom ODA Data Source

Purpose

The Open Data Access (ODA) component is an open and flexible data access framework that provides a common way for a consumer application to access data from heterogeneous data sources. Any data provider who wants to be consumed by such ODA consumer applications may implement a custom ODA data provider by implementing the ODA runtime and design-time driver extension points.

Extension Points Involved

  • ODA Runtime extension point:
    • org.eclipse.datatools.connectivity.oda.dataSource
  • ODA Design-time extension points:
    • org.eclipse.datatools.connectivity.oda.design.ui.dataSource
    • org.eclipse.datatools.connectivity.connectionProfile
    • org.eclipse.ui.propertyPages

Java API Interfaces/Classes

  • ODA runtime data access
    • org.eclipse.datatools.connectivity.oda package (Java interfaces for runtime data access)
    • org.eclipse.datatools.connectivity.oda.manifest package (utility classes to access the content of own plug-in manifest)
  • ODA Design-time API for defining a data source and data set design
    • org.eclipse.datatools.connectivity.oda.design package
    • org.eclipse.datatools.connectivity.oda.design.ui.designsession.DesignSessionUtil class (utility class to manipulate ODA Design API objects during an ODA design session)
  • ODA Designer API for contributing provider-specific design UI pages
    • org.eclipse.datatools.connectivity.oda.design.ui.wizards package
    • org.eclipse.datatools.connectivity.oda.design.ui.pages.impl package (default implementation to define a data source design)
    • org.eclipse.datatools.connectivity.oda.design.ui.manifest package (utility classes to access the content of own plugin manifest)

Exemplary Clients

  • CSV Flat-file data source -
    • org.eclipse.datatools.connectivity.oda.flatfile and org.eclipse.datatools.connectivity.oda.flatfile.ui plug-ins
  • XML data source -
    • org.eclipse.datatools.enablement.oda.xml and org.eclipse.datatools.enablement.oda.xml.ui plug-ins
  • BIRT JDBC data source -
    • org.eclipse.birt.report.data.oda.jdbc and org.eclipse.birt.report.data.oda.jdbc.ui plug-ins

Back to the top