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.
Difference between revisions of "Connectivity Callisto Features"
(→General) |
(Editing to make consistent with other feature page formats) |
||
| Line 13: | Line 13: | ||
===The following features are ''under consideration'' for Connectivity Callisto:=== | ===The following features are ''under consideration'' for Connectivity Callisto:=== | ||
====General==== | ====General==== | ||
| − | + | * Remove org.eclipse.ui dependency from org.eclipse.datatools.connectivity. [https://bugs.eclipse.org/bugs/show_bug.cgi?id=125962 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. [https://bugs.eclipse.org/bugs/show_bug.cgi?id=114415 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. [https://bugs.eclipse.org/bugs/show_bug.cgi?id=137122 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 (non-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. [https://bugs.eclipse.org/bugs/show_bug.cgi?id=137123 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) | |
| − | + | * 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] | |
| − | + | ** 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. [https://bugs.eclipse.org/bugs/show_bug.cgi?id=137125 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>My preference would be to try to implement all features that might affect APIs in an additive way. | <rjc>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> | 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> | ||
Revision as of 09:00, 18 April 2006
← Back to Connectivity Main Page
Contents
The following features are committed for Connectivity Callisto:
The following features are under construction for Connectivity Callisto:
WTP Support
- Database connectivity for all WTP/rbd databases
- Notes: <JG>For vendor support pack.</JG>
- Refinements to connection dialog
- WTP 'Database Explorer' support. Port all:
- Features
- Extension points
The following features are under consideration for Connectivity Callisto:
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 (non-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)
- Requirements:
- 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)
- Requirements:
- 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)
- Requirements:
<rjc>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>