RE: Re[2]: R: R: frustrated - jdbc: No suitable driver

! 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

Re: Re[2]: R: R: frustrated - jdbc: No suitable driver

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

SV: Re[2]: R: R: frustrated - jdbc: No suitable driver

. 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

RE: Re[2]: R: R: frustrated - jdbc: No suitable driver

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

RE: Re[2]: R: R: frustrated - jdbc: No suitable driver

-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

Re[2]: R: R: frustrated - jdbc: No suitable driver

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

RE: R: R: frustrated - jdbc: No suitable driver

e you do? After all maybe I am being dense and missing something. :) Al -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Jeff Schnitzer Sent: Wednesday, January 31, 2001 12:15 AM To: Orion-Interest Subject: RE: R: R: frustrated - jdbc: No suitable driver

SV: R: R: frustrated - jdbc: No suitable driver

To: Orion-Interest <[EMAIL PROTECTED]> Sent: Tuesday, January 30, 2001 9:28 PM Subject: Re: R: R: frustrated - jdbc: No suitable driver Jeff, I disagree. Part of the benefit of a DataSource is that it can abstract the actual driver or database being used. If I can ask a DataSource for a data

SV: R: R: frustrated - jdbc: No suitable driver

ception(ex); } // .. do some JDBC stuff conn.close(); Hope this helps you further :=) Have fun!! Klaus Myrseth -Opprinnelig melding- Fra: Burr Sutter [mailto:[EMAIL PROTECTED]] Sendt: 31. januar 2001 15:21 Til: Orion-Interest Emne: Re: R: R: frustrated - jdbc: No suitable driver

Re: R: R: frustrated - jdbc: No suitable driver

CTED]> Sent: Tuesday, January 30, 2001 9:28 PM Subject: Re: R: R: frustrated - jdbc: No suitable driver Jeff, I disagree. Part of the benefit of a DataSource is that it can abstract the actual driver or database being used. If I can ask a DataSource for a database connection and not have

RE: R: R: frustrated - jdbc: No suitable driver

dynamically downloading the class files is slow anyways :-) :-) :-) Jeff >-Original Message- >From: Tom Mitchell [mailto:[EMAIL PROTECTED]] >Sent: Tuesday, January 30, 2001 6:29 PM >To: Orion-Interest >Subject: Re: R: R: frustrated - jdbc: No suitable driver > > >Jeff,

Re: R: R: frustrated - jdbc: No suitable driver

rations, and licensing issues? You know > you're going to need the classes anyways, package them with the client. > > Jeff > > >-Original Message- > >From: Tom Mitchell [mailto:[EMAIL PROTECTED]] > >Sent: Tuesday, January 30, 2001 9:08 AM > >To: Orio

RE: R: R: frustrated - jdbc: No suitable driver

-- >From: Tom Mitchell [mailto:[EMAIL PROTECTED]] >Sent: Tuesday, January 30, 2001 9:08 AM >To: Orion-Interest >Subject: Re: R: R: frustrated - jdbc: No suitable driver > > >Again, thanks for your replies. > >What is curious to me is that the driver performs fine within a jsp

Re: R: R: frustrated - jdbc: No suitable driver

/> > > you should lookup "jdbc/HypersonicDS", and you should have the driver > classes in your /orion/lib directory. > > Giustino > > -Messaggio originale- > Da: Tom Mitchell [mailto:[EMAIL PROTECTED]] > Inviato: martedì 30 gennaio 2001 12.24 > A:

R: R: frustrated - jdbc: No suitable driver

-Messaggio originale- Da: Tom Mitchell [mailto:[EMAIL PROTECTED]] Inviato: martedì 30 gennaio 2001 12.24 A: Orion-Interest Oggetto: Re: R: frustrated - jdbc: No suitable driver Thanks for the reply. That is exactly how I am initializing the context in my client application: Hashtabl

Re: R: frustrated - jdbc: No suitable driver

Thanks for the reply. That is exactly how I am initializing the context in my client application: Hashtable ht = new Hashtable(); ht.put(Context.INITIAL_CONTEXT_FACTORY, "com.evermind.server.ApplicationClientInitialContextFactory"); ht.put(Context.PROVIDER_URL, "ormi://192.168.

R: frustrated - jdbc: No suitable driver

Try initializing the context this way: ... Properties props = new Properties(); props.setProperty("java.naming.factory.initial","com.evermind.server.Applica tionClientInitialContextFactory"); props.setProperty("java.naming.provider.url", "ormi://localhost/app-name"); props.setProperty("java.naming