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

Bug 365359

Summary:	Projects using jt400 and a default schema get "No Suitable Driver" error
Product:	z_Archived	Reporter:	Joe Pluta <joepluta>
Component:	EDT	Assignee:	Justin Spadea <jspadea>
Status:	RESOLVED FIXED	QA Contact:
Severity:	major
Priority:	P3	CC:	joepluta, jspadea, smythew
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:

Description Joe Pluta

2011-12-01 15:02:12 EST

Build Identifier: EGL: 0.7.0.v201111272101-1CT-Fiv5_LLLMAz-6K_J

If a project uses a connection that uses jt400.jar to connect to a database, and that connection is set up to have a default schema, then when the EGL code is executed it fails to connect to the database, issuing the error "No suitable driver for jdbc:as400:...".  The workedaround is to remove the default schema in the connection and issue a setCurrentSchema to the datasource in the EGL code.

Reproducible: Always

Steps to Reproduce:
1. Create a connection to an i5/OS database using the Java Toolbox
2. Set a schema in the connection
3. Try to use a datasource using that connection in your EGL

Comment 1 Justin Spadea

2012-01-04 09:51:44 EST

Fixed SysLib.java and IDEResourceLocator.java in org.eclipse.edt.runtime.java to load the driver class before invoking setCurrentSchema (which opens a connection).

Comment 2 Lisa Lasher

2012-04-04 22:40:56 EDT

This bug is fixed in 0.8. Please verify the fix in any recent 0.8 build, and close the bug.   If you still see a problem, you can reopen the bug with additional information.