Is this true: JNDI equals Connection Pooling

[Ed Carrington]

I have JNDI set up in my Tomcat server.xml and working with an Oracle 9i database for my web app. Is JNDI equal to Connection Pooling? If so I assume I have successfully implemented Connection Pooling for my web app?
[ November 19, 2007: Message edited by: Ed Carrington ]

[Jeanne Boyarsky]

Originally posted by Ed Carrington:
Is JNDI equal to Connection Pooling?

No. The JNDI is a place to look up the connection pool resource.

If so I assume I have successfully implemented Connection Pooling for my web app?

If you are doing a JNDI lookup to get the connection pool, you have successfully implemented connection pooling.

[arulk pillai]

It is an intrface to directory servers like LDAP etc. For example JDBC is an interface to your database servers. Likewise JNDI is an interface to directory servers like LDAP. Using JNDI you can look up objects, user credentials, printer information etc stored in the underlying LDAP implementations. LDAPs are generally faster to search than Database servers.

You can also look up JDBC connection pools, JMS queues etc using JNDI. Most application servers have a JNDI implementation to facilitate lookups.
[ November 19, 2007: Message edited by: arulk pillai ]

[Ed Carrington]

Thanks,

So this below example is how JNDI lookups a connection pool?

server.xml(C:\jakarta-tomcat-4.1.27\conf)

<Context path="/DBTest" docBase="DBTest" 
        debug="5" reloadable="true" crossContext="true"> 
 
  <Logger className="org.apache.catalina.logger.FileLogger" 
             prefix="localhost_DBTest_log." suffix=".txt" 
             timestamp="true"/> 
 
  <Resource name="jdbc/TestDB" 
               auth="Container" 
               type="javax.sql.DataSource"/> 
 
 <Resource name="jdbc/myoracle" auth="Container" 
              type="javax.sql.DataSource"/>  
 
<ResourceParams name="jdbc/myoracle"> 
  <parameter> 
    <name>factory</name> 
    <value>org.apache.commons.dbcp.BasicDataSourceFactory</value> 
  </parameter> 
  <parameter> 
    <name>driverClassName</name> 
    <value>oracle.jdbc.OracleDriver</value> 
  </parameter> 
  <parameter> 
    <name>url</name> 
    <value>jdbc  :-o	  racle:thin:@127.0.0.1:1521:mysid</value> 
  </parameter> 
  <parameter> 
    <name>username</name> 
    <value>scott</value> 
  </parameter> 
  <parameter> 
    <name>password</name> 
    <value>tiger</value> 
  </parameter> 
  <parameter> 
    <name>maxActive</name> 
    <value>20</value> 
  </parameter> 
  <parameter> 
    <name>maxIdle</name> 
    <value>10</value> 
  </parameter> 
  <parameter> 
    <name>maxWait</name> 
    <value>-1</value> 
  </parameter> 
</ResourceParams> 
</Context> 

web.xml

<resource-ref> 
 <description>Oracle Datasource example</description> 
 <res-ref-name>jdbc/myoracle</res-ref-name> 
 <res-type>javax.sql.DataSource</res-type> 
 <res-auth>Container</res-auth> 
</resource-ref>  

database connection part

 Context initContext = new InitialContext(); 
Context envContext  = (Context)initContext.lookup("java:/comp/env"); 
DataSource ds = (DataSource)envContext.lookup("jdbc/myoracle"); 
Connection conn = ds.getConnection(); 
//etc.  

[ November 19, 2007: Message edited by: Ed Carrington ]