Community
Participate
Working Groups
Ability to pre-populate a connection UI with driver definitions. Need additional information from Larry. This may already exist with the ability to auto-create a default instance of a particular driver template at startup and then reference default drivers by id in the driver drop-down.
Note that in order to pre-populate valid driver definitions, a facility needs to exist that allows adopters to provide the location of the driver jars at runtime. Static paths do not work as the jars are commonly located inside Eclipse plug-ins/fragments and the version numbers and hence the absolute paths to those drivers can change over time. The facility needs to be able to allow the location to be calculated at runtime so that the plug-in relative path can be converted into an absolute path.
In addition, the creation of default driver definitions should only occur once - when the workspace is created. Currently it occurs each time the workbench is started, which has the unfortunate effect of recreating default driver definitions if one is missing (i.e. you start up a workbench, delete a driver you don't want that was created by default, restart the workbench, and there it is again). We need to change this so it occurs once and then doesn't reoccur.
Created attachment 86961 [details] Patch fixes creating default drivers once and only once in a workspace lifecycle Hey Larry... Here's a patch that takes care of the issue with creating default drivers over and over again. Can you take a look? If it's ok, let me know and I'll work on John's solution of having a class that provides driver property values once this is delivered. --Fitz
Delivered 1st patch for default driver definition creation at workspace startup to the 1.6 head stream.
Moving this to M6 as part of the usability effort
Larry, has this bug been addressed by the driverValuesProvider work?
Yes, you can resolve this defect.
Marking as fixed.
Closing bugs
