Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 356792

Summary: TestConnection from DD Editor's Resource Binding page
Product: z_Archived Reporter: Zhi Zhu <zhuzhi>
Component: EDTAssignee: Zhi Zhu <zhuzhi>
Status: CLOSED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: chenzhh, smythew, tdramsey, tww
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard:

Description Zhi Zhu CLA 2011-09-06 06:05:00 EDT
Build Identifier: TestConnection from DD Editor's Resource Binding page

Now we can get the below connection related items from the page:
org.eclipse.datatools.connectivity.db.vendor = DB2 UDB
org.eclipse.datatools.connectivity.db.URL=jdbc:db2://rbdsrv1.rtp.raleigh.ibm.com:50000/ECLIPSE:retrieveMessagesFromServerOnGetMessage=true;
org.eclipse.datatools.connectivity.db.password=
org.eclipse.datatools.connectivity.db.databaseName=
org.eclipse.datatools.connectivity.db.username=
org.eclipse.datatools.connectivity.db.driverClass=com.ibm.db2.jcc.DB2Driver,
org.eclipse.datatools.connectivity.db.URL
org.eclipse.datatools.connectivity.db.version=V9.1, 
org.eclipse.datatools.connectivity.db.vendor=DB2 UDB]

But cannot get below items:
 jarList=
 
So we need to add a field for class location jar if we want to success implementing TestConnetion on the page

Currently we support the following databases:
 1>Derby
 2>Db2
 3>Oracle
 4>SqlServer
 5>informix

Do we need to support other DBs, if so,please list them out here

Reproducible: Always
Comment 1 Will Smythe CLA 2011-09-06 09:17:29 EDT
Based on a past conversation with Tim, we are no longer going to limit the databases that can be used by an EGL application. Assuming it supports standard JDBC operations, it should be allowed. It is up to the developer to write any custom SQL for cases when the SQL we use for specific statements does not work.
Comment 2 Zhi Zhu CLA 2011-09-07 01:12:22 EDT
For the 'ResourceBinding' page to show SQL database binding messages, I suggest to save the following fields to *.egldd file
 
1> name: the id of the item in all sql database binding list, default to dbVerdor+" "+dbVersion
2>dbms(SQL Database): default to dbVerdor+" "+dbVersion
3>dbProfileID: is used in TestConnection to distinguish different DB, is also used in dropdown list to select list, the field should not be changed by user and can select to not display it on user interface.
4>JDBC driver class
5>connection url
6>JNDI name
7>databse name
8>user name
9>password

10>Default schema: the field seems useless and cannot be applied to all database, so I suggest removing it

How about your opinion about this?
Comment 3 Zhi Zhu CLA 2011-09-14 05:42:28 EDT
fix it
Comment 4 Zhi Zhu CLA 2011-10-11 20:37:50 EDT
close it