Skip to main content
Jump to: navigation, search

Use Case - Create a Custom ODA Data Source

Revision as of 22:49, 17 October 2006 by (Talk | contribs) (Creating a Custom ODA Data Source)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)


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.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
    • package
    • class (utility class to manipulate ODA Design API objects during an ODA design session)
  • ODA Designer API for contributing provider-specific design UI pages
    • package
    • package (default implementation to define a data source design)
    • 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 -
    • and plug-ins

Back to the top