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 Callisto Features"

(→‎General)
 
(23 intermediate revisions by 4 users not shown)
Line 1: Line 1:
 
←[[Connectivity | Back to Connectivity Main Page]]
 
←[[Connectivity | Back to Connectivity Main Page]]
 +
{{Callisto Deprecation Notice}}
 
===The following features are committed for Connectivity Callisto:===
 
===The following features are committed for Connectivity Callisto:===
−
 
+
====JUnit Tests====
−
===The following features are ''under consideration'' for Connectivity Callisto:===
+
<PMC>Add JUnit tests to SQL Dev</PMC>
−
====WTP Support====
+
====WTP Parity====
−
* Database connectivity for all WTP/rbd databases
+
<JG>'''Note:''' The details and timing of these items need to be clarified by the connectivity team.</JG>
 +
* Database connectivity for all WTP/rdb databases
 
** Notes: <JG>For ''vendor support'' pack.</JG>
 
** Notes: <JG>For ''vendor support'' pack.</JG>
 
* Refinements to connection dialog
 
* Refinements to connection dialog
Line 10: Line 12:
 
** Features
 
** Features
 
** Extension points
 
** Extension points
−
 
 
====General====
 
====General====
−
# Remove org.eclipse.ui dependency from org.eclipse.datatools.connectivity.
+
* Remove org.eclipse.ui dependency from org.eclipse.datatools.connectivity. [https://bugs.eclipse.org/bugs/show_bug.cgi?id=125962 Bugzilla 125962]
−
#* Requirements
+
** Requirements: Allow connectivity functionality to be used within a ''headless'' environment.
−
#*: Allow connectivity functionality to be used within a "headless" environment.
+
** Development Estimate: 2-3 days
−
#* Development Estimate
+
** Possible Start Date: April 10
−
#*: 2-3 days
+
** API Impacts: IConnectionProfile.add/removePropertyListener().  (currently depends on org.eclipse.ui.IPropertyListener)
−
#* Possible Start Date
+
** UI Impacts: None.
−
#*: April 10
+
** Can Complete by 4/7: Unlikely (might not be a concern if it weren't for the API impact).
−
#* API Impacts
+
* Prevent storing of authentication data within the workspace. [https://bugs.eclipse.org/bugs/show_bug.cgi?id=114415 Bugzilla 114415]
−
#*: IConnectionProfile.add/removePropertyListener().  (currently depends on org.eclipse.ui.IPropertyListener)
+
** Requirements: Give the user the option to store or not store authentication information within the workspace.
−
#* UI Impacts
+
** Development Estimate: 3 weeks +/- 1 week (swag)
−
#*: None.
+
** Possible Start Date: TBD
−
#* Can Complete by 4/7
+
** API Impacts: Unknown.  Presumably additive.
−
#*: Unlikely (might not be a concern if it weren't for the API impact).
+
** UI Impacts: Generic DB new wizard and connection details property page.
−
# Prevent storing of authentication data within the workspace.
+
** Can Complete by 4/7: Unlikely (need resources)
−
#* Requirements
+
* Add a pingFactory attribute to connectionProfile element within org.eclipse.datatools.connectivity.connectionProfile extension. [https://bugs.eclipse.org/bugs/show_bug.cgi?id=137122 Bugzilla 137122]
−
#*: Give the user the option to store or not store authentication information within the workspace.
+
** Requirements: Simplify connection profile extension point.
−
#* Development Estimate
+
** Development Estimate: 2 days
−
#*: 3 weeks +/- 1 week (swag)
+
** Possible Start Date: April 5-10
−
#* Possible Start Date
+
** API Impacts: Impacts connectionProfile extension point schema (additive).
−
#*: TBD
+
** UI Impacts: None.
−
#* API Impacts
+
** Can Complete by 4/7: Possibly (4/13 is probably more reasonable)
−
#*: Unknown.  Presumably additive.
+
* Add an element to org.eclipse.datatools.connectivity.connectionProfile that would allow developers to associate an adapter for a specified connection type.  For example, a SQL model adapter for java.sql.Connection objects. [https://bugs.eclipse.org/bugs/show_bug.cgi?id=137123 Bugzilla 137123]
−
#* UI Impacts
+
** Requirements:
−
#*: Generic DB new wizard and connection details property page.
+
***Reduce the number of connection factories associated with a connection profile.  
−
#* Can Complete by 4/7
+
***Promote reuse of existing connections (e.g. DB profiles create two java.sql.Connection objects).
−
#*: Unlikely (need resources)
+
***Allow views to be associated with connection types as opposed to connection profile types.
−
# Add a pingFactory attribute to connectionProfile element within org.eclipse.datatools.connectivity.connectionProfile extension.
+
** Development Estimate: 1 week
−
#* Requirements
+
** Possible Start Date: April 5-10
−
#*: Simplify connection profile extension point.
+
** API Impacts: Impacts connection profile APIs (changes are additive).
−
#* Development Estimate
+
** UI Impacts: None.
−
#*: 2 days
+
** Can Complete by 4/7: Unlikely (4/13 is probably more reasonable)
−
#* Possible Start Date
+
 
−
#*: April 5-10
+
* Extend ODA run-time capability to use externalized data source connection info. [https://bugs.eclipse.org/bugs/show_bug.cgi?id=137359 Bugzilla 137359]
−
#* API Impacts
+
** Requirements: Allow an ODA consumer application, such as J2EE application, to extend the ODA consumer framework to provide application-specific service to obtain configurable, externalized property values, for use by an ODA driver to connect to a data source.
−
#*: Impacts connectionProfile extension point schema (non-additive).
+
** Development Estimate: 2-3 days
−
#* UI Impacts
+
** Possible Start Date: May 8
−
#*: None.
+
** API Impacts: New provisional extension point and Java interface  (additive)
−
#* Can Complete by 4/7
+
** UI Impacts: None.
−
#*: Possibly (4/13 is probably more reasonable)
+
** Can Complete by RC3 milestone.
−
# Add an element to org.eclipse.datatools.connectivity.connectionProfile that would allow developers to associate an adapter for a specified connection type.  For example, a SQL model adapter for java.sql.Connection objects.
+
 
−
#* Requirements
+
===The following features are ''under consideration'' for Connectivity Callisto:===
−
#*: Reduce the number of connection factories associated with a connection profile.
+
===General===
−
#*: Promote reuse of existing connections (e.g. DB profiles create two java.sql.Connection objects).
+
* Change the way version information is stored within connection profile instances.  Move the information from being stored within the base properties to a version specific properties group. [https://bugs.eclipse.org/bugs/show_bug.cgi?id=137124 Bugzilla 137124]
−
#*: Allow views to be associated with connection types as opposed to connection profile types.
+
** Requirements: A fix was put in to prevent this information from being overwritten by the connection details page which effectively prevents properties from being removed from the profile.  This fix needs to be reverted and replaced by this proposed solution.
−
#* Development Estimate
+
** Development Estimate: 3-5 days
−
#*: 1 week
+
** Possible Start Date: April 5-10
−
#* Possible Start Date
+
** API Impacts: None. (Impacts lookup keys for retrieving this information, but this is not currently defined as public API.)
−
#*: April 5-10
+
** UI Impacts: None.
−
#* API Impacts
+
** Can Complete by 4/7: Unlikely (May not be an issue since this is not really a feature.)
−
#*: Impacts connection profile APIs (changes are additive).
+
* Develop an extension to the connection profile framework to enable start/stop functionality for profile instances. [https://bugs.eclipse.org/bugs/show_bug.cgi?id=137125 Bugzilla 137125]
−
#* UI Impacts
+
** Requirements:
−
#*: None.
+
***Allow developers to specify information that can be used for starting/restarting/stopping servers represented by connection profile instances.
−
#* Can Complete by 4/7
+
*** Provide consistent UI through connection profile framework (i.e. DSE) for accessing start/restart/stop functionality.
−
#*: Unlikely (4/13 is probably more reasonable)
+
** Development Estimate: 3 weeks +/- 1 week (swag)
−
# Change the way version information is stored within connection profile instances.  Move the information from being stored within the base properties to a version specific properties group.
+
** Possible Start Date: TBD
−
#* Requirements
+
** API Impacts: Should be implemented as an extension to existing framework.
−
#*: A fix was put in to prevent this information from being overwritten by the connection details page which effectively prevents properties from being removed from the profile.  This fix needs to be reverted and replaced by this proposed solution.
+
** UI Impacts: Yes.  (New actions in DSE.  Base class implementations for implementing start/stop/restart functionality).
−
#* Development Estimate
+
** Can Complete by 4/7: Unlikely (need resources)
−
#*: 3-5 days
+
* Extension point wizard for org.eclipse.datatools.connectivity.connectionProfile.
−
#* Possible Start Date
+
** Requirements:
−
#*: April 5-10
+
***Accelerate development of connection profile extensions.
−
#* API Impacts
+
*** Minimize errors related to references between extension elements.
−
#*: None. (Impacts lookup keys for retrieving this information, but this is not currently defined as public API.)
+
** Development Estimate: 3 weeks (swag)
−
#* UI Impacts
+
** Possible start date: TBD
−
#*: None.
+
** API Impacts: None.
−
#* Can Complete by 4/7
+
** UI Impacts: None (this would be new UI, most likely distributed with a DTP SDK feature)
−
#*: Unlikely (May not be an issue since this is not really a feature.)
+
** Can Complete by 4/7: Unlikely (need resources)
−
# Develop an extension to the connection profile framework to enable start/stop functionality for profile instances.
+
 
−
#* Requirements
+
<rjc>'''Note:'''My preference would be to try to implement all features that might affect APIs in an additive way.
−
#*: Allow developers to specify information that can be used for starting/restarting/stopping servers represented by connection profile instances.
+
−
#*: Provide consistent UI through connection profile framework (i.e. DSE) for accessing start/restart/stop functionality.
+
−
#* Development Estimate
+
−
#*: 3 weeks +/- 1 week (swag)
+
−
#* Possible Start Date
+
−
#*: TBD
+
−
#* API Impacts
+
−
#*: Should be implemented as an extension to existing framework.
+
−
#* UI Impacts
+
−
#*: Yes.  (New actions in DSE.  Base class implementations for implementing start/stop/restart functionality).
+
−
#* Can Complete by 4/7
+
−
#*: Unlikely (need resources)
+
−
# Extension point wizard for org.eclipse.datatools.connectivity.connectionProfile.
+
−
#* Requirements
+
−
#*: Accelerate development of connection profile extensions.
+
−
#*: Minimize errors related to references between extension elements.
+
−
#* Development Estimate
+
−
#*: 3 weeks (swag)
+
−
#* Possible start date
+
−
#*: TBD
+
−
#* API Impacts
+
−
#*: None.
+
−
#* UI Impacts
+
−
#*: None (this would be new UI, most likely distributed with a DTP SDK feature)
+
−
#* Can Complete by 4/7
+
−
#*: Unlikely (need resources)
+
−
My preference would be to try to implement all features that might affect APIs in an additive way.
+
  
−
I think it would also be nice if we could implement an extension point wizard for the connectionProfile extension.  I don't think this could be completed prior to Callisto, but think it might be something that could be provided as an "extra" for those willing to try it (i.e. an alpha version of a post-Callisto feature).
+
I think it would also be nice if we could implement an extension point wizard for the connectionProfile extension.  I don't think this could be completed prior to Callisto, but think it might be something that could be provided as an "extra" for those willing to try it (i.e. an alpha version of a post-Callisto feature).</rjc>

Latest revision as of 22:55, 26 August 2007

← Back to Connectivity Main Page

Note: This page discusses topics related to the 2006 Callisto Simultaneous Release. Most of the Callisto pages are deprecated. You are urged to find current information on pages related to the 2007 effort, currently named the Europa Simultaneous Release.

The following features are committed for Connectivity Callisto:

JUnit Tests

<PMC>Add JUnit tests to SQL Dev</PMC>

WTP Parity

<JG>Note: The details and timing of these items need to be clarified by the connectivity team.</JG>

  • Database connectivity for all WTP/rdb databases
    • Notes: <JG>For vendor support pack.</JG>
  • Refinements to connection dialog
  • WTP 'Database Explorer' support. Port all:
    • Features
    • Extension points

General

  • Remove org.eclipse.ui dependency from org.eclipse.datatools.connectivity. Bugzilla 125962
    • Requirements: Allow connectivity functionality to be used within a headless environment.
    • Development Estimate: 2-3 days
    • Possible Start Date: April 10
    • API Impacts: IConnectionProfile.add/removePropertyListener(). (currently depends on org.eclipse.ui.IPropertyListener)
    • UI Impacts: None.
    • Can Complete by 4/7: Unlikely (might not be a concern if it weren't for the API impact).
  • Prevent storing of authentication data within the workspace. Bugzilla 114415
    • Requirements: Give the user the option to store or not store authentication information within the workspace.
    • Development Estimate: 3 weeks +/- 1 week (swag)
    • Possible Start Date: TBD
    • API Impacts: Unknown. Presumably additive.
    • UI Impacts: Generic DB new wizard and connection details property page.
    • Can Complete by 4/7: Unlikely (need resources)
  • Add a pingFactory attribute to connectionProfile element within org.eclipse.datatools.connectivity.connectionProfile extension. Bugzilla 137122
    • Requirements: Simplify connection profile extension point.
    • Development Estimate: 2 days
    • Possible Start Date: April 5-10
    • API Impacts: Impacts connectionProfile extension point schema (additive).
    • UI Impacts: None.
    • Can Complete by 4/7: Possibly (4/13 is probably more reasonable)
  • Add an element to org.eclipse.datatools.connectivity.connectionProfile that would allow developers to associate an adapter for a specified connection type. For example, a SQL model adapter for java.sql.Connection objects. Bugzilla 137123
    • Requirements:
      • Reduce the number of connection factories associated with a connection profile.
      • Promote reuse of existing connections (e.g. DB profiles create two java.sql.Connection objects).
      • Allow views to be associated with connection types as opposed to connection profile types.
    • Development Estimate: 1 week
    • Possible Start Date: April 5-10
    • API Impacts: Impacts connection profile APIs (changes are additive).
    • UI Impacts: None.
    • Can Complete by 4/7: Unlikely (4/13 is probably more reasonable)
  • Extend ODA run-time capability to use externalized data source connection info. Bugzilla 137359
    • Requirements: Allow an ODA consumer application, such as J2EE application, to extend the ODA consumer framework to provide application-specific service to obtain configurable, externalized property values, for use by an ODA driver to connect to a data source.
    • Development Estimate: 2-3 days
    • Possible Start Date: May 8
    • API Impacts: New provisional extension point and Java interface (additive)
    • UI Impacts: None.
    • Can Complete by RC3 milestone.

The following features are under consideration for Connectivity Callisto:

General

  • Change the way version information is stored within connection profile instances. Move the information from being stored within the base properties to a version specific properties group. Bugzilla 137124
    • Requirements: A fix was put in to prevent this information from being overwritten by the connection details page which effectively prevents properties from being removed from the profile. This fix needs to be reverted and replaced by this proposed solution.
    • Development Estimate: 3-5 days
    • Possible Start Date: April 5-10
    • API Impacts: None. (Impacts lookup keys for retrieving this information, but this is not currently defined as public API.)
    • UI Impacts: None.
    • Can Complete by 4/7: Unlikely (May not be an issue since this is not really a feature.)
  • Develop an extension to the connection profile framework to enable start/stop functionality for profile instances. Bugzilla 137125
    • Requirements:
      • Allow developers to specify information that can be used for starting/restarting/stopping servers represented by connection profile instances.
      • Provide consistent UI through connection profile framework (i.e. DSE) for accessing start/restart/stop functionality.
    • Development Estimate: 3 weeks +/- 1 week (swag)
    • Possible Start Date: TBD
    • API Impacts: Should be implemented as an extension to existing framework.
    • UI Impacts: Yes. (New actions in DSE. Base class implementations for implementing start/stop/restart functionality).
    • Can Complete by 4/7: Unlikely (need resources)
  • Extension point wizard for org.eclipse.datatools.connectivity.connectionProfile.
    • Requirements:
      • Accelerate development of connection profile extensions.
      • Minimize errors related to references between extension elements.
    • Development Estimate: 3 weeks (swag)
    • Possible start date: TBD
    • API Impacts: None.
    • UI Impacts: None (this would be new UI, most likely distributed with a DTP SDK feature)
    • Can Complete by 4/7: Unlikely (need resources)

<rjc>Note:My preference would be to try to implement all features that might affect APIs in an additive way.

I think it would also be nice if we could implement an extension point wizard for the connectionProfile extension. I don't think this could be completed prior to Callisto, but think it might be something that could be provided as an "extra" for those willing to try it (i.e. an alpha version of a post-Callisto feature).</rjc>

Retrieved from "https://wiki.eclipse.org/index.php?title=Connectivity_Callisto_Features&oldid=48035"

This page was last modified 22:55, 26 August 2007 by Daniel Spiewak. Based on work by Linda Chan, Linda Chan and Rob Cernich and others.

Copyright © Eclipse Foundation, Inc. All Rights Reserved.