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

[Allen Fogleson]

Uhmmm, I agree, I was confused because someone said they still needed the
JDBC drivers on the client, and assuming you use the portable method of
DataSources, there should be no reason that they would need to have the JDBC
drivers, it is all handled container side with the datasource.

Al

-----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.

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 totally safe) only the JNDI Datasource name will be
found. It's up to you to set a security schema for the connection with
the app server, but at least is one problem less to solve.

--
Best regards,
 Rafael                            mailto:[EMAIL PROTECTED]