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]
- REFERENCE WAR CLASSES FROM EJB-JAR FILES Josh P Motto
- RE: REFERENCE WAR CLASSES FROM EJB-JAR FILES Mike Cannon-Brookes
- RE: REFERENCE WAR CLASSES FROM EJB-JAR FI... Gary Shea
- RE: REFERENCE WAR CLASSES FROM EJB-JA... Mike Cannon-Brookes
- RE: REFERENCE WAR CLASSES FROM E... Gary Shea
- RE: R: R: frustrated - jdbc: No suitable driver Jeff Schnitzer
- Re: R: R: frustrated - jdbc: No suitable driver Tom Mitchell
- Re: R: R: frustrated - jdbc: No suitable driv... Burr Sutter
- RE: R: R: frustrated - jdbc: No suitable driver Jeff Schnitzer
- RE: R: R: frustrated - jdbc: No suitable driver Allen Fogleson
- RE: Re[2]: R: R: frustrated - jdbc: No suitab... Rafael Alvarez
- RE: Re[2]: R: R: frustrated - jdbc: No su... Allen Fogleson
- SV: R: R: frustrated - jdbc: No suitable driver Klaus . Myrseth
- SV: R: R: frustrated - jdbc: No suitable driver Klaus . Myrseth
- RE: Re[2]: R: R: frustrated - jdbc: No suitable driver Jeff Schnitzer
- Re: Re[2]: R: R: frustrated - jdbc: No suitable d... Jesse Kuhnert
- SV: Re[2]: R: R: frustrated - jdbc: No suitable driver Klaus . Myrseth
- RE: Re[2]: R: R: frustrated - jdbc: No suitable driver Daniel Cardin