!
Daniel
-Message d'origine-
De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Envoyé : 5 février, 2001 08:06
À : Orion-Interest
Objet : SV: Re[2]: R: R: frustrated - jdbc: No suitable driver
You shouls check out the getConnection implementation on the datasource.
It gets a referen
plement such a proxy? Or is
> it just WebLogic - allowing the behavior described in the original post?
> Or is WebLogic doing http-type classloading to get the JDBC driver into
> the client (a prospect I am considering less likely the more I think
> about it)?
>
> Ever curiou
.
Klaus
-Opprinnelig melding-
Fra: Jeff Schnitzer [mailto:[EMAIL PROTECTED]]
Sendt: 5. februar 2001 12:17
Til: Orion-Interest
Emne: RE: Re[2]: R: R: frustrated - jdbc: No suitable driver
I'm fully prepared to believe that my understanding of how this works is
wrong, but if so it r
t it)?
Ever curious,
Jeff
>-Original Message-
>From: Allen Fogleson [mailto:[EMAIL PROTECTED]]
>Sent: Sunday, February 04, 2001 10:46 AM
>To: Orion-Interest
>Subject: RE: Re[2]: R: R: frustrated - jdbc: No suitable driver
>
>
>Uhmmm, I agree, I was confused bec
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Rafael Alvarez
Sent: Sunday, February 04, 2001 10:24 AM
To: Orion-Interest
Subject: Re[2]: R: R: frustrated - jdbc: No suitable driver
Hello Allen,
DataSources gives you one advantage on the client side: Security
Hello Allen,
DataSources gives you one advantage on the client side: Security.
If you use a direct JDBC connection to a Database, your username,
password and URL have to be placed in your class. A Datasource hides
all those details, so if some one decompile your class (even JAXed
classes are not
