|Subject||Re: [Firebird-Java] Re: Jaybird deploy problem: ”No suitable driver”|
> --- In Firebird-Java@yahoogroups.com, "lbhifi" <lbhifi@...> wrote:Then either you did not actually load the driver, or your URL is of the wrong format. The way JDBC works is that the driver registers its URL prefixes, and the DriverManager selects that driver based on those URLs (I believe the driver can still reject an URL if it is not wellformed for the driver).
> > Before I describe the layout, I would like to persue a different lead. I
> just tried to create a new database connection using JDevelopers tool for
> that, and when I test the connection I get the same "No suitable driver"
> Made it work by using a older version of jaybird, but still no luck with
> the deployed jar. I tried putting the jaybird jar in the same path as the
> deployed jar and adding ClassPath: jaybird-full-2.1.6.jar to the manifest.mf
> in the deployed jar, but then it throws a driver-not-found exception.
So if you did not actually register the driver (Class.forName) or use the wrong URL, then it simply will not work.
> I then tried to go the jdbc-odbc bridge way, but the very same odbc dsnCould it be a 64 bit Windows 2003? Because there it really matters if you are using the 64 bit java or 32 bit java, and if you created the DSN using 64 bit or 32 bit ODBC manager.
> which works fine on my XP, will not work on the 2003 Server.
GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT!
Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01