I was writing a bean managed entity bean and I came across this "Connection
pool" feature of weblogic.
According to weblogic documentation I can create a connection pool by
specifying these properties.
******************************
weblogic.jdbc.connectionPool.ejbPool=\
url=jdbc:cloudscape:ejbdemo,\
driver=COM.cloudscape.core.JDBCDriver,\
loginDelaySecs=1,\
initialCapacity=2,\
maxCapacity=2,\
capacityIncrement=1,\
props=user=none;password=none;server=none
weblogic.allow.reserve.weblogic.jdbc.connectionPool.ejbPool=\
guest,joe,jill
*******************************************
Then to use this connection pool the code inside EJB will be something like
**********************************************************
Class.forName("weblogic.jdbc.jts.Driver").newInstance();
Connection con = DriverManager.getConnection("jdbc:weblogic:jts:ejbPool");
*********************************************************
But this the way I create the connection. Instead of mentioning
"ejbPool" in the url I mention my database URL.
What is the advantage of using the pool? Anyway I need to load the Driver in
each of entity bean.
Any hints will be highly appreciated.
Regards,
Rajesh Singh
Analyst
Goldman Sachs
10 Hanover Sqaure
NY 10004
212-855-6151
Singh, Rajesh.vcf
