Hello Kristian, The Class.forName did it! Thanks a lot. I'd never used 10.1.1.0 before so I didn't know about these tricks :-)
Tiago ----- Original Message ---- From: Kristian Waagan <[email protected]> To: [email protected] Sent: Tue, 20 July, 2010 14:34:23 Subject: Re: No suitable driver found for ... On 20.07.10 14:55, Tiago Espinha wrote: > Hello all, > > I'm doing some old client testing for DERBY-4746 and I've ran into a problem > that I can't seem to be able to solve. Basically, I tested my trunk server > against a 10.5 client and everything was fine. But then when I test it > against >a > 10.1.1.0 client, I get the following: > > No suitable driver found for jdbc:derby://localhost:1527/client1011;create=true > > I'm using eclipse and I simply add all the external jars (inside the bin >folder) > into the project. This procedure worked with 10.5 but 10.1.1.0 isn't liking it > for some reason. Does anyone know what might be the cause of this? I get this > exception just as I do: > > Connection conn = >DriverManager.getConnection("jdbc:derby://localhost:1527/client1011;create=true"); >; > Hi Tiago, I don't know why it would be special for 10.1.1.0, but have you done Class.forName("org.apache.derby.jdbc.ClientDriver")? Does your test code work with 10.5 if you run with Java 1.4 or 5.0? Not sure when we added the driver auto-loading.... Was it in Derby 10.3? Regards, -- Kristian > > Thanks, > Tiago > > > > >
