Greg, Thanks for your inputs. Thanks for taking the time to explain about castor. I will make all the changes you guys had suggested and post the results.
Thanks again. Vijay -----Original Message----- From: Gregory Block [mailto:[EMAIL PROTECTED] Sent: Monday, May 02, 2005 8:32 AM To: [email protected] Subject: Re: [castor-user] Transaction locks and muti threaded access On 1 May 2005, at 08:20, Werner Guttmann wrote: > Mike, > > have a look at > > http://castor.codehaus.org/pooling.html#Jakarta-Commons-DBCP--- > BasicDataSource > > which has details about how to use and configure DBCP with Castor and > Tomcat. Wrt 'prepared statement cache', Gregory seems to be referring > to the fact that DBCP is JDBC 3.0-compliant product as as such has to > support caching of prepared statements. This basically allows the JDBC > driver to maintain a pool of prepared statements across all > connections. > Correct. DBCP setup is generally outside of the scope of this list, but basically, here's my two cent description: 1) Use tomcat 5.5, because mucking about in server.xml sucks. 2) Create a META-INF directory in your WAR deploy scripts, and put a context.xml in it. 3) In that context.xml, describe all of the things you want to be made available via JNDI to your application. These include things like UserTransaction and TransactionManager (for those of us using JOTM), all your database connection pools as datasources, etc. You can also add your JDO factory here, should you choose to do so. 4) Configure Castor to load those JNDI names to retrieve connections. Hit the deploy button, and bob's your uncle.
