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

2001-02-05 Thread Jeff Schnitzer
- 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 because someone said they still needed the JDBC drivers on the client, and assuming you use

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

2001-02-05 Thread Klaus . Myrseth
. 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 raises

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

2001-02-05 Thread Jesse Kuhnert
ely the more I think about 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

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

2001-02-05 Thread Daniel Cardin
! Daniel -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Envoy : 5 fvrier, 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 reference it pass

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

2001-02-04 Thread Rafael Alvarez
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: Re[2]: R: R: frustrated - jdbc: No suitable driver

2001-02-04 Thread Allen Fogleson
-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: R: R: frustrated - jdbc: No suitable driver

2001-02-03 Thread Allen Fogleson
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 While

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

2001-01-31 Thread Burr Sutter
, 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 to care about which client-side driver

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

2001-01-31 Thread Klaus . Myrseth
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

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

2001-01-31 Thread Klaus . Myrseth
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 to care a

R: frustrated - jdbc: No suitable driver

2001-01-30 Thread DeVincentiis Giustino
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");

Re: R: frustrated - jdbc: No suitable driver

2001-01-30 Thread Tom Mitchell
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,

R: R: frustrated - jdbc: No suitable driver

2001-01-30 Thread DeVincentiis Giustino
iginale----- 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: Hashtable ht = ne

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

2001-01-30 Thread Tom Mitchell
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: Orion-Interest Subject: Re: R: R: frustrated - jdbc: No suitable driver Again, thanks

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

2001-01-30 Thread Jeff Schnitzer
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, I disagree. Part of the benefit of a DataSource