Bug 204623 - Generic connection profile type should only be for generic JDBC driver definition
Summary: Generic connection profile type should only be for generic JDBC driver defini...
Status: NEW
Alias: None
Product: Data Tools
Classification: Tools
Component: Connectivity (show other bugs)
Version: 1.6   Edit
Hardware: PC All
: P3 normal (vote)
Target Milestone: future   Edit
Assignee: dtp.connectivity-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-09-25 19:39 EDT by Larry Dunnell CLA
Modified: 2007-09-26 15:48 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Larry Dunnell CLA 2007-09-25 19:39:17 EDT 
Currently, the generic connection profile wizard provides a way to connect to any database even if that database already provides a connection profile wizard.  This causes user confusion as it provides two ways to configure a connection to the same database and also means there are redundant driver definition templates displayed in the Driver Definition Preference page since there is a driver definition template defined for each wizard.

To solve this, the generic connection profile type will only provide one driver definition template that will be associated to the generic JDBC database definition.  In order to enable users to continue to connect to databases using that database's database definition, connection profile wizards will be implemented for those datbases that do not currently provide one.  Implementing the wizards should be greatly simplified by taking advantage of the shared connection profile wizard being provided by https://bugs.eclipse.org/bugs/show_bug.cgi?id=204620.
Comment 1 Larry Dunnell CLA 2007-09-25 19:40:07 EDT 
This is a post-Ganymede requirement.