Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 365359 - Projects using jt400 and a default schema get "No Suitable Driver" error
Summary: Projects using jt400 and a default schema get "No Suitable Driver" error
Status: RESOLVED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: EDT (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Justin Spadea CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-01 15:02 EST by Joe Pluta CLA
Modified: 2017-02-23 14:20 EST (History)
3 users (show)

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 Joe Pluta CLA 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 CLA 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 CLA 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.