Difference between revisions of "Connectivity Europa Features"

From Eclipsepedia

Jump to: navigation, search
(Europa Requirements)
Line 5: Line 5:
 
The following are the areas of focus for the Europa release.  NOTE: This information is preliminary.
 
The following are the areas of focus for the Europa release.  NOTE: This information is preliminary.
 
==Release Goals==
 
==Release Goals==
===Europa Requirements===
+
===Europa Specific Requirements===
 
These are derived from the [[Europa Simultaneous Release#Requirements For Participation | Europa release requirements]]
 
These are derived from the [[Europa Simultaneous Release#Requirements For Participation | Europa release requirements]]
 
*Separate runtime and SDK feature sets
 
*Separate runtime and SDK feature sets

Revision as of 15:25, 21 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.

Contents

Release Goals

Europa Specific 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

BZ 174877

  • 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.

Slightly related:

Information from DatabaseMetaData should supercede statically defined settings in DatabaseDefinition, where/when applicable (BZ 166526).
DSE Specialization for SQL Model Content

Define standard approaches for specializing SQL model content (BZ 162291)

  • Overriding default container names
  • Adding content to default containers
  • Specializing content structure
Integrate Work Offline Mode

Integrate Work Offline mode with core connectivity framework (BZ 175005)

WTP/RDB Adopter Migration

  • Ensure feature compatibility
  • 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. (BZ 175007)
  • Modify JDBC catalog objects to recycle objects during refresh (BZ 170579)

Community Outreach

  • Document contribution process

General

  • Update Derby catalog loader to use new catalog loader utility classes (BZ 167471)