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 "Connectivity Europa Features"

(Europa Requirements)
(Database Recognition)
Line 28: Line 28:
 
*Integrate with ConnectionInfo connection factories
 
*Integrate with ConnectionInfo connection factories
 
*Investigate whether or not driver definition templates may be simplified (i.e. remove vendor specific driver definitions)
 
*Investigate whether or not driver definition templates may be simplified (i.e. remove vendor specific driver definitions)
 +
The [[Proposed solution|proposed solution]].
 +
 
====DSE Specialization for SQL Model Content====
 
====DSE Specialization for SQL Model Content====
 
Define standard approaches for specializing SQL model content
 
Define standard approaches for specializing SQL model content

Revision as of 18:08, 20 February 2007

Back to Connectivity Main Page

Back to DTP 1.5 Project Plan

The following are the areas of focus for the Europa release. NOTE: This information is preliminary.

Europa Requirements

These are derived from the Europa release requirements

  • Separate runtime and SDK feature sets
  • All plugins must specify required JVM version Completed
Target for M5
  • All plugins should be JARed Completed
Target for M5
Top level bugzilla entry 172550

API Promotion

Elevate provisional API to platform status.

Unit Test Coverage

Improve unit test coverage for public API.

Documentation

Improve developer documentation.

API Revisions

Planned revisions to public API. These revisions may be released as provisional API.

Note: API changes must be completed by M6

Database Recognition

  • Enable database recognition extension point
  • Integrate with ConnectionInfo connection factories
  • Investigate whether or not driver definition templates may be simplified (i.e. remove vendor specific driver definitions)

The proposed solution.

DSE Specialization for SQL Model Content

Define standard approaches for specializing SQL model content

  • Overriding default container names
  • Adding content to default containers
  • Specializing content structure

Integrate Work Offline Mode

Integrate Work Offline mode with core connectivity framework

WTP/RDB Adopter Migration

  • Ensure feature compatibility
    • Connection selection dialog (BZ ######)
  • Provide technical support to adopters

ODA Enhancements

  • Integrate connection profile framework with ODA runtime
  • Add support for multi-dimensional data sources (experimental API)

Generic Database Support

  • Expand generic DDL generation to include SPs, UDFs, etc.
  • Modify JDBC catalog objects to recycle objects during refresh

Community Outreach

  • Document contribution process

General

  • Update Derby catalog loader to use new catalog loader utility classes

Copyright © Eclipse Foundation, Inc. All Rights Reserved.