Gustavo Saramago wrote:
>
> I wonder why the JDBC specification delegates the responsability for
> implementing connection pools to the driver vendor. The result is
> the we got implementation classes like OracleConnectionPoolDataSource,
> that reduce the portability of the code.
>
If you use an application server that allows you to configure JDBC 2.0
DataSources, then your code doesn't need to include references to
vendor-specific implementation classes and can remain portable. That is, you
configure the DataSource giving it a logical name, then use JNDI in your
code to retrieve the DataSource using that logical name. (When you configure
the DataSource you tell it which vendor-specific class to use. If you change
JDBC drivers you only change the configuration data, not your code).
ServletExec 4.1 supports configuring JDBC 2.0 DataSources--I'm sure there
are other application servers that do also, or will in the near future.
Vince Bonfanti
New Atlanta Communications
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
For digest: mailto [EMAIL PROTECTED] with body: "set JSP-INTEREST DIGEST".
Some relevant FAQs on JSP/Servlets can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
