| A Message to ODA Extension Developers [message #39489] |
Mon, 23 May 2005 23:10  |
Eclipse User |
|
|
|
--------------538061ED22B38D44BE6D48C2
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
As part of our internal review of the Open Data Access (ODA) public API
and incorporating feedback from the community, we have refined the ODA
extension point schema and the runtime driver's Java interfaces.
The main functional aspects of ODA remain the same. The changes are
primarily to provide a more consistent naming convention and
stream-lined API. We do recognize that this comes at a rather late
stage in the Release 1 development cycle. However, having a more
refined API could encourage more implementations of the ODA extension
point. This would also help set the stage for further extension to be
used by other ODA consumer applications.
The revised ODA extension point and Java interfaces are now checked into
the BIRT CVS source repository.
The ODA extension plug-ins supplied with the BIRT installation, such as
org.eclipse.birt.report.data.oda.jdbc, have been updated as well.
Related documentation can be found in the source.
* org.eclipse.birt.data.oda/schema/datasource.exsd for the new ODA
extension point schema
* org.eclipse.birt.data.oda package Javadoc reference
More reference documentation will be provided on the BIRT web site
later.
For those who have worked with the previous ODA extension point and API
for custom data sources, below is a summarized list of changes made:
ODA Extension Point and Schema changes:
1. Merged the odaDriverModel and odaDriverRuntime extension points
into a new ODA extension point; its schema is defined in
org.eclipse.birt.data.oda/schema/dataSource.exsd
1. both data source and data set are now uniquely identified by
an extension "id" attribute, which should be a
package-qualified name. The id attribute replaces the
previous "driverName" and "dataSetType" attributes.
2. removed display name attributes from the UI
|
|
|
| Re: A Message to ODA Extension Developers [message #39616 is a reply to message #39489] |
Tue, 24 May 2005 11:19  |
| Eclipse User |
|
|
|
Thanks for the heads up :D
Linda Chan wrote:
> As part of our internal review of the Open Data Access (ODA) public API
> and incorporating feedback from the community, we have refined the ODA
> extension point schema and the runtime driver's Java interfaces.
> The main functional aspects of ODA remain the same. The changes are
> primarily to provide a more consistent naming convention and
> stream-lined API. We do recognize that this comes at a rather late
> stage in the Release 1 development cycle. However, having a more
> refined API could encourage more implementations of the ODA extension
> point. This would also help set the stage for further extension to be
> used by other ODA consumer applications.
>
> The revised ODA extension point and Java interfaces are now checked into
> the BIRT CVS source repository.
> The ODA extension plug-ins supplied with the BIRT installation, such as
> org.eclipse.birt.report.data.oda.jdbc, have been updated as well.
>
> Related documentation can be found in the source.
>
> * org.eclipse.birt.data.oda/schema/datasource.exsd for the new ODA
> extension point schema
> * org.eclipse.birt.data.oda package Javadoc reference
>
> More reference documentation will be provided on the BIRT web site later.
>
>
> For those who have worked with the previous ODA extension point and API
> for custom data sources, below is a summarized list of changes made:
>
> ODA Extension Point and Schema changes:
>
> 1. Merged the odaDriverModel and odaDriverRuntime extension points
> into a new ODA extension point; its schema is defined in
> org.eclipse.birt.data.oda/schema/dataSource.exsd
> 1. both data source and data set are now uniquely identified by
> an extension "id" attribute, which should be a
> package-qualified name. The id attribute replaces the
> previous "driverName" and "dataSetType" attributes.
> 2. removed display name attributes from the UI’s dataSource
> extension point schema. The end user visible data source and
> data set name are now defined in the
> org.eclipse.birt.data.oda.dataSource extension point.
> 3. renamed connectionFactoryClass attribute to driverClass
> 4. changed dataSource's odaVersion attribute data type to a String
>
> Renamed interfaces:
>
> * IConnectionFactory to IDriver
> * IStatement to IQuery
> * IAdvancedStatement to IAdvancedQuery
>
> Removed interface:
>
> * IConnectionMetaData
>
> Moved and renamed methods:
>
> * IConnectionMetaData.getMaxStatements() to IConnection.getMaxQueries()
> * IConnectionMetaData.getMaxConnections() to
> IConnection.getMaxConnections()
>
> Renamed methods:
>
> * IConnection.createStatement() to newQuery()
> * IConnection.isOpened() to isOpen()
>
> Removed methods:
>
> * the IStatement.getParameterType methods
>
> Implementation of IParameterMetaData is now required for drivers
> * that support parameters IStatement.setPropertyInfo( Properties info )
> * IConnection.getMetaData() that returns IConnectionMetaData
>
> Changed method protocol:
>
> * changed IDriver.getConnection method argument to take an unique
> data source element id that is defined in the extension plugin
> manifest, instead of a connection class name
> * encapsulated IDriver.setLogConfiguration method arguments to a new
> class LogConfiguration
>
>
> That's all! :-)
>
> Linda
> and BIRT Data Engine team
>
|
|
|
Powered by
FUDForum. Page generated in 0.05775 seconds
Home